0s autopkgtest [05:02:00]: starting date and time: 2025-02-22 05:02:00+0000 0s autopkgtest [05:02:00]: git checkout: 325255d2 Merge branch 'pin-any-arch' into 'ubuntu/production' 0s autopkgtest [05:02:00]: host juju-7f2275-prod-proposed-migration-environment-9; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.l89ud5z8/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:glib2.0 --apt-upgrade libfprint --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=glib2.0/2.83.4-1 -- lxd -r lxd-armhf-10.145.243.240 lxd-armhf-10.145.243.240:autopkgtest/ubuntu/plucky/armhf 51s autopkgtest [05:02:51]: testbed dpkg architecture: armhf 53s autopkgtest [05:02:53]: testbed apt version: 2.9.14ubuntu1 58s autopkgtest [05:02:58]: @@@@@@@@@@@@@@@@@@@@ test bed setup 60s autopkgtest [05:03:00]: testbed release detected to be: None 69s autopkgtest [05:03:09]: updating testbed package index (apt update) 71s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [110 kB] 72s Get:2 http://ftpmaster.internal/ubuntu plucky InRelease [249 kB] 72s Get:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease [110 kB] 72s Get:4 http://ftpmaster.internal/ubuntu plucky-security InRelease [110 kB] 72s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [508 kB] 72s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [13.5 kB] 72s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [3120 B] 72s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [80.1 kB] 72s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf Packages [125 kB] 72s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf Components [26.6 kB] 72s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/restricted armhf Packages [760 B] 72s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/restricted armhf Components [216 B] 72s Get:13 http://ftpmaster.internal/ubuntu plucky-proposed/universe armhf Packages [424 kB] 72s Get:14 http://ftpmaster.internal/ubuntu plucky-proposed/universe armhf Components [213 kB] 72s Get:15 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse armhf Packages [1796 B] 72s Get:16 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse armhf Components [1076 B] 72s Get:17 http://ftpmaster.internal/ubuntu plucky/universe Sources [21.0 MB] 74s Get:18 http://ftpmaster.internal/ubuntu plucky/main Sources [1384 kB] 74s Get:19 http://ftpmaster.internal/ubuntu plucky/restricted Sources [16.3 kB] 74s Get:20 http://ftpmaster.internal/ubuntu plucky/multiverse Sources [298 kB] 74s Get:21 http://ftpmaster.internal/ubuntu plucky/main armhf Packages [1370 kB] 74s Get:22 http://ftpmaster.internal/ubuntu plucky/main armhf Components [401 kB] 74s Get:23 http://ftpmaster.internal/ubuntu plucky/restricted armhf Packages [2900 B] 74s Get:24 http://ftpmaster.internal/ubuntu plucky/restricted armhf Components [196 B] 74s Get:25 http://ftpmaster.internal/ubuntu plucky/universe armhf Packages [15.1 MB] 74s Get:26 http://ftpmaster.internal/ubuntu plucky/universe armhf Components [3953 kB] 74s Get:27 http://ftpmaster.internal/ubuntu plucky/multiverse armhf Packages [173 kB] 74s Get:28 http://ftpmaster.internal/ubuntu plucky/multiverse armhf Components [39.8 kB] 74s Get:29 http://ftpmaster.internal/ubuntu plucky-updates/main armhf Components [208 B] 74s Get:30 http://ftpmaster.internal/ubuntu plucky-updates/restricted armhf Components [212 B] 74s Get:31 http://ftpmaster.internal/ubuntu plucky-updates/universe armhf Components [212 B] 74s Get:32 http://ftpmaster.internal/ubuntu plucky-updates/multiverse armhf Components [212 B] 74s Get:33 http://ftpmaster.internal/ubuntu plucky-security/main armhf Components [204 B] 74s Get:34 http://ftpmaster.internal/ubuntu plucky-security/restricted armhf Components [208 B] 74s Get:35 http://ftpmaster.internal/ubuntu plucky-security/universe armhf Components [208 B] 74s Get:36 http://ftpmaster.internal/ubuntu plucky-security/multiverse armhf Components [208 B] 81s Fetched 45.7 MB in 7s (6298 kB/s) 82s Reading package lists... 88s autopkgtest [05:03:28]: upgrading testbed (apt dist-upgrade and autopurge) 91s Reading package lists... 91s Building dependency tree... 91s Reading state information... 92s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 92s Starting 2 pkgProblemResolver with broken count: 0 92s Done 93s Entering ResolveByKeep 93s 93s The following packages were automatically installed and are no longer required: 93s libapt-pkg6.0t64 libassuan0 libicu74 libnsl2 libpython3.12-minimal 93s libpython3.12-stdlib libunwind8 linux-headers-6.11.0-8 93s linux-headers-6.11.0-8-generic python3.12 python3.12-minimal 93s Use 'apt autoremove' to remove them. 94s The following NEW packages will be installed: 94s gcc-15-base libapt-pkg7.0 libicu76 libjemalloc2 libpython3.13-minimal 94s libpython3.13-stdlib linux-headers-6.12.0-15 linux-headers-6.12.0-15-generic 94s login.defs openssl-provider-legacy python3-bcrypt python3.13 94s python3.13-minimal 94s The following packages will be upgraded: 94s apparmor apport apport-core-dump-handler appstream apt apt-utils base-files 94s base-passwd bash bash-completion bind9-dnsutils bind9-host bind9-libs 94s binutils binutils-arm-linux-gnueabihf binutils-common bsdextrautils bsdutils 94s btrfs-progs busybox-initramfs busybox-static ca-certificates cloud-init 94s cloud-init-base console-setup console-setup-linux coreutils cron 94s cron-daemon-common cryptsetup-bin curl dash dbus dbus-bin dbus-daemon 94s dbus-session-bus-common dbus-system-bus-common dbus-user-session dhcpcd-base 94s diffutils dirmngr distro-info dmsetup dpkg dpkg-dev dracut-install e2fsprogs 94s e2fsprogs-l10n ed eject ethtool fdisk fwupd gcc-14-base gettext-base 94s gir1.2-girepository-2.0 gir1.2-glib-2.0 gir1.2-packagekitglib-1.0 gnupg 94s gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpgconf gpgsm gpgv 94s groff-base gzip htop ibverbs-providers inetutils-telnet init 94s init-system-helpers initramfs-tools initramfs-tools-bin initramfs-tools-core 94s iproute2 iptables iputils-ping iputils-tracepath kbd keyboard-configuration 94s keyboxd kpartx krb5-locales libapparmor1 libappstream5 libapt-pkg6.0t64 94s libarchive13t64 libatomic1 libbinutils libblkid1 libblockdev-crypto3 94s libblockdev-fs3 libblockdev-loop3 libblockdev-mdraid3 libblockdev-nvme3 94s libblockdev-part3 libblockdev-swap3 libblockdev-utils3 libblockdev3 libbpf1 94s libc-bin libc6 libcap-ng0 libcbor0.10 libcom-err2 libcrypt1 libcryptsetup12 94s libctf-nobfd0 libctf0 libcurl3t64-gnutls libcurl4t64 libdbus-1-3 94s libdebconfclient0 libdevmapper1.02.1 libdpkg-perl libedit2 libext2fs2t64 94s libfdisk1 libffi8 libfribidi0 libftdi1-2 libfwupd3 libgcc-s1 94s libgirepository-1.0-1 libglib2.0-0t64 libglib2.0-bin libglib2.0-data 94s libgnutls30t64 libgpg-error-l10n libgpg-error0 libgpgme11t64 94s libgssapi-krb5-2 libgstreamer1.0-0 libgudev-1.0-0 libhogweed6t64 libibverbs1 94s libicu74 libip4tc2 libip6tc2 libjson-glib-1.0-0 libjson-glib-1.0-common 94s libk5crypto3 libkrb5-3 libkrb5support0 libldap-common libldap2 liblsof0 94s liblz4-1 libmaxminddb0 libmount1 libncurses6 libncursesw6 libnetplan1 94s libnettle8t64 libnewt0.52 libnftables1 libnftnl11 libnpth0t64 libnspr4 94s libnss-systemd libnss3 libnvme1t64 libp11-kit0 libpackagekit-glib2-18 94s libpam-systemd libpcap0.8t64 libperl5.40 libplymouth5 libpng16-16t64 94s libpolkit-agent-1-0 libpolkit-gobject-1-0 libprotobuf-c1 libpython3-stdlib 94s libpython3.12-minimal libpython3.12-stdlib libqmi-glib5 libqmi-proxy 94s libreadline8t64 libsasl2-2 libsasl2-modules libsasl2-modules-db libselinux1 94s libsemanage-common libsemanage2 libsframe1 libsmartcols1 libss2 libssl3t64 94s libstdc++6 libsystemd-shared libsystemd0 libtasn1-6 libtinfo6 libtraceevent1 94s libtraceevent1-plugin libudev1 libudisks2-0 libunistring5 liburcu8t64 94s libusb-1.0-0 libuuid1 libvolume-key1 libwrap0 libxdmcp6 libxkbcommon0 94s libxml2 libxtables12 libxxhash0 libyaml-0-2 libzstd1 linux-headers-generic 94s locales login logsave lshw lsof lto-disabled-list make mawk motd-news-config 94s mount multipath-tools nano ncurses-base ncurses-bin ncurses-term 94s netcat-openbsd netplan-generator netplan.io nftables openssl packagekit 94s packagekit-tools passwd pci.ids perl perl-base perl-modules-5.40 94s pinentry-curses plymouth plymouth-theme-ubuntu-text polkitd pollinate 94s powermgmt-base psmisc publicsuffix python-apt-common python-babel-localedata 94s python3 python3-apport python3-apt python3-attr python3-babel 94s python3-certifi python3-chardet python3-cryptography python3-distro-info 94s python3-gdbm python3-gi python3-idna python3-jinja2 python3-json-pointer 94s python3-jsonpatch python3-jsonschema python3-jwt python3-launchpadlib 94s python3-lazr.uri python3-minimal python3-more-itertools python3-netplan 94s python3-newt python3-oauthlib python3-openssl python3-pkg-resources 94s python3-problem-report python3-pygments python3-referencing python3-requests 94s python3-rich python3-setuptools python3-software-properties python3-urllib3 94s python3-wadllib python3.12 python3.12-gdbm python3.12-minimal 94s python3.13-gdbm readline-common rsync rsyslog software-properties-common 94s systemd systemd-cryptsetup systemd-resolved systemd-sysv systemd-timesyncd 94s sysvinit-utils tar telnet tmux tzdata ubuntu-minimal ubuntu-pro-client 94s ubuntu-pro-client-l10n ubuntu-standard ucf udev udisks2 ufw 94s unattended-upgrades usb.ids util-linux uuid-runtime vim-common vim-tiny 94s whiptail xauth xfsprogs xxd zstd 94s 323 upgraded, 13 newly installed, 0 to remove and 0 not upgraded. 94s Need to get 148 MB of archives. 94s After this operation, 204 MB of additional disk space will be used. 94s Get:1 http://ftpmaster.internal/ubuntu plucky/main armhf motd-news-config all 13.6ubuntu1 [5168 B] 94s Get:2 http://ftpmaster.internal/ubuntu plucky/main armhf gcc-15-base armhf 15-20250213-1ubuntu1 [53.2 kB] 94s Get:3 http://ftpmaster.internal/ubuntu plucky/main armhf libgcc-s1 armhf 15-20250213-1ubuntu1 [40.6 kB] 94s Get:4 http://ftpmaster.internal/ubuntu plucky/main armhf libc6 armhf 2.40-4ubuntu1 [2866 kB] 94s Get:5 http://ftpmaster.internal/ubuntu plucky/main armhf libcrypt1 armhf 1:4.4.38-1 [91.7 kB] 94s Get:6 http://ftpmaster.internal/ubuntu plucky/main armhf base-files armhf 13.6ubuntu1 [75.3 kB] 94s Get:7 http://ftpmaster.internal/ubuntu plucky/main armhf bash armhf 5.2.37-1ubuntu1 [677 kB] 94s Get:8 http://ftpmaster.internal/ubuntu plucky/main armhf bsdutils armhf 1:2.40.2-14ubuntu1 [110 kB] 94s Get:9 http://ftpmaster.internal/ubuntu plucky/main armhf coreutils armhf 9.5-1ubuntu1 [1275 kB] 94s Get:10 http://ftpmaster.internal/ubuntu plucky/main armhf dash armhf 0.5.12-12ubuntu1 [87.4 kB] 94s Get:11 http://ftpmaster.internal/ubuntu plucky/main armhf diffutils armhf 1:3.10-2 [172 kB] 94s Get:12 http://ftpmaster.internal/ubuntu plucky/main armhf libxxhash0 armhf 0.8.3-2 [30.8 kB] 94s Get:13 http://ftpmaster.internal/ubuntu plucky/main armhf liblz4-1 armhf 1.10.0-3 [57.2 kB] 94s Get:14 http://ftpmaster.internal/ubuntu plucky/main armhf openssl-provider-legacy armhf 3.4.1-1ubuntu1 [29.5 kB] 95s Get:15 http://ftpmaster.internal/ubuntu plucky/main armhf libssl3t64 armhf 3.4.1-1ubuntu1 [1771 kB] 95s Get:16 http://ftpmaster.internal/ubuntu plucky/main armhf libzstd1 armhf 1.5.6+dfsg-2 [266 kB] 95s Get:17 http://ftpmaster.internal/ubuntu plucky/main armhf libstdc++6 armhf 15-20250213-1ubuntu1 [725 kB] 95s Get:18 http://ftpmaster.internal/ubuntu plucky/main armhf systemd-timesyncd armhf 257.2-3ubuntu1 [42.1 kB] 95s Get:19 http://ftpmaster.internal/ubuntu plucky/main armhf dbus-session-bus-common all 1.16.0-1ubuntu1 [53.1 kB] 95s Get:20 http://ftpmaster.internal/ubuntu plucky/main armhf systemd-sysv armhf 257.2-3ubuntu1 [11.9 kB] 95s Get:21 http://ftpmaster.internal/ubuntu plucky/main armhf libpam-systemd armhf 257.2-3ubuntu1 [238 kB] 95s Get:22 http://ftpmaster.internal/ubuntu plucky/main armhf dbus-user-session armhf 1.16.0-1ubuntu1 [9684 B] 95s Get:23 http://ftpmaster.internal/ubuntu plucky/main armhf libapparmor1 armhf 4.1.0~beta5-0ubuntu5 [48.7 kB] 95s Get:24 http://ftpmaster.internal/ubuntu plucky/main armhf libcap-ng0 armhf 0.8.5-4 [13.8 kB] 95s Get:25 http://ftpmaster.internal/ubuntu plucky/main armhf libselinux1 armhf 3.7-3ubuntu2 [73.2 kB] 95s Get:26 http://ftpmaster.internal/ubuntu plucky/main armhf dbus-system-bus-common all 1.16.0-1ubuntu1 [54.3 kB] 95s Get:27 http://ftpmaster.internal/ubuntu plucky/main armhf dbus-bin armhf 1.16.0-1ubuntu1 [37.9 kB] 95s Get:28 http://ftpmaster.internal/ubuntu plucky/main armhf dbus armhf 1.16.0-1ubuntu1 [28.1 kB] 95s Get:29 http://ftpmaster.internal/ubuntu plucky/main armhf dbus-daemon armhf 1.16.0-1ubuntu1 [111 kB] 95s Get:30 http://ftpmaster.internal/ubuntu plucky/main armhf libdbus-1-3 armhf 1.16.0-1ubuntu1 [162 kB] 95s Get:31 http://ftpmaster.internal/ubuntu plucky/main armhf systemd-resolved armhf 257.2-3ubuntu1 [315 kB] 95s Get:32 http://ftpmaster.internal/ubuntu plucky/main armhf libncurses6 armhf 6.5+20250125-2 [88.8 kB] 95s Get:33 http://ftpmaster.internal/ubuntu plucky/main armhf libncursesw6 armhf 6.5+20250125-2 [118 kB] 95s Get:34 http://ftpmaster.internal/ubuntu plucky/main armhf libtinfo6 armhf 6.5+20250125-2 [91.9 kB] 95s Get:35 http://ftpmaster.internal/ubuntu plucky/main armhf bsdextrautils armhf 2.40.2-14ubuntu1 [94.2 kB] 95s Get:36 http://ftpmaster.internal/ubuntu plucky/main armhf eject armhf 2.40.2-14ubuntu1 [63.4 kB] 95s Get:37 http://ftpmaster.internal/ubuntu plucky/main armhf fdisk armhf 2.40.2-14ubuntu1 [157 kB] 95s Get:38 http://ftpmaster.internal/ubuntu plucky/main armhf libblkid1 armhf 2.40.2-14ubuntu1 [169 kB] 95s Get:39 http://ftpmaster.internal/ubuntu plucky/main armhf libmount1 armhf 2.40.2-14ubuntu1 [194 kB] 95s Get:40 http://ftpmaster.internal/ubuntu plucky/main armhf libsmartcols1 armhf 2.40.2-14ubuntu1 [137 kB] 95s Get:41 http://ftpmaster.internal/ubuntu plucky/main armhf libuuid1 armhf 2.40.2-14ubuntu1 [41.0 kB] 95s Get:42 http://ftpmaster.internal/ubuntu plucky/main armhf util-linux armhf 2.40.2-14ubuntu1 [1190 kB] 95s Get:43 http://ftpmaster.internal/ubuntu plucky/main armhf uuid-runtime armhf 2.40.2-14ubuntu1 [63.7 kB] 95s Get:44 http://ftpmaster.internal/ubuntu plucky/main armhf libfdisk1 armhf 2.40.2-14ubuntu1 [217 kB] 95s Get:45 http://ftpmaster.internal/ubuntu plucky/main armhf mount armhf 2.40.2-14ubuntu1 [158 kB] 95s Get:46 http://ftpmaster.internal/ubuntu plucky/main armhf readline-common all 8.2-6 [56.5 kB] 95s Get:47 http://ftpmaster.internal/ubuntu plucky/main armhf libreadline8t64 armhf 8.2-6 [131 kB] 95s Get:48 http://ftpmaster.internal/ubuntu plucky/main armhf systemd-cryptsetup armhf 257.2-3ubuntu1 [126 kB] 95s Get:49 http://ftpmaster.internal/ubuntu plucky/main armhf libsystemd-shared armhf 257.2-3ubuntu1 [2203 kB] 95s Get:50 http://ftpmaster.internal/ubuntu plucky/main armhf libnss-systemd armhf 257.2-3ubuntu1 [164 kB] 95s Get:51 http://ftpmaster.internal/ubuntu plucky/main armhf systemd armhf 257.2-3ubuntu1 [3028 kB] 95s Get:52 http://ftpmaster.internal/ubuntu plucky/main armhf udev armhf 257.2-3ubuntu1 [1402 kB] 95s Get:53 http://ftpmaster.internal/ubuntu plucky/main armhf libudev1 armhf 257.2-3ubuntu1 [193 kB] 95s Get:54 http://ftpmaster.internal/ubuntu plucky/main armhf libdevmapper1.02.1 armhf 2:1.02.201-1ubuntu1 [137 kB] 95s Get:55 http://ftpmaster.internal/ubuntu plucky/main armhf libcryptsetup12 armhf 2:2.7.5-1ubuntu2 [246 kB] 95s Get:56 http://ftpmaster.internal/ubuntu plucky/main armhf libsystemd0 armhf 257.2-3ubuntu1 [494 kB] 95s Get:57 http://ftpmaster.internal/ubuntu plucky/main armhf libapt-pkg6.0t64 armhf 2.9.29 [1086 kB] 95s Get:58 http://ftpmaster.internal/ubuntu plucky/main armhf tar armhf 1.35+dfsg-3.1 [240 kB] 95s Get:59 http://ftpmaster.internal/ubuntu plucky/main armhf dpkg armhf 1.22.11ubuntu4 [1242 kB] 95s Get:60 http://ftpmaster.internal/ubuntu plucky/main armhf gzip armhf 1.13-1ubuntu2 [98.1 kB] 95s Get:61 http://ftpmaster.internal/ubuntu plucky/main armhf ncurses-bin armhf 6.5+20250125-2 [179 kB] 95s Get:62 http://ftpmaster.internal/ubuntu plucky/main armhf perl-modules-5.40 all 5.40.1-2 [3217 kB] 95s Get:63 http://ftpmaster.internal/ubuntu plucky/main armhf libperl5.40 armhf 5.40.1-2 [4135 kB] 95s Get:64 http://ftpmaster.internal/ubuntu plucky/main armhf perl armhf 5.40.1-2 [262 kB] 95s Get:65 http://ftpmaster.internal/ubuntu plucky/main armhf perl-base armhf 5.40.1-2 [1667 kB] 95s Get:66 http://ftpmaster.internal/ubuntu plucky/main armhf libdebconfclient0 armhf 0.274ubuntu1 [11.2 kB] 95s Get:67 http://ftpmaster.internal/ubuntu plucky/main armhf base-passwd armhf 3.6.6 [53.4 kB] 95s Get:68 http://ftpmaster.internal/ubuntu plucky/main armhf init-system-helpers all 1.68 [39.0 kB] 95s Get:69 http://ftpmaster.internal/ubuntu plucky/main armhf libc-bin armhf 2.40-4ubuntu1 [542 kB] 96s Get:70 http://ftpmaster.internal/ubuntu plucky/main armhf ncurses-base all 6.5+20250125-2 [25.8 kB] 96s Get:71 http://ftpmaster.internal/ubuntu plucky/main armhf ncurses-term all 6.5+20250125-2 [276 kB] 96s Get:72 http://ftpmaster.internal/ubuntu plucky/main armhf kbd armhf 2.7.1-2ubuntu1 [214 kB] 96s Get:73 http://ftpmaster.internal/ubuntu plucky/main armhf console-setup-linux all 1.226ubuntu3 [1880 kB] 96s Get:74 http://ftpmaster.internal/ubuntu plucky/main armhf console-setup all 1.226ubuntu3 [110 kB] 96s Get:75 http://ftpmaster.internal/ubuntu plucky/main armhf keyboard-configuration all 1.226ubuntu3 [212 kB] 96s Get:76 http://ftpmaster.internal/ubuntu plucky/main armhf sysvinit-utils armhf 3.14-1ubuntu1 [35.1 kB] 96s Get:77 http://ftpmaster.internal/ubuntu plucky/main armhf libapt-pkg7.0 armhf 2.9.30ubuntu1 [1067 kB] 96s Get:78 http://ftpmaster.internal/ubuntu plucky/main armhf apt armhf 2.9.30ubuntu1 [1392 kB] 96s Get:79 http://ftpmaster.internal/ubuntu plucky/main armhf apt-utils armhf 2.9.30ubuntu1 [214 kB] 96s Get:80 http://ftpmaster.internal/ubuntu plucky/main armhf libgpg-error-l10n all 1.51-3 [8800 B] 96s Get:81 http://ftpmaster.internal/ubuntu plucky/main armhf libgpg-error0 armhf 1.51-3 [64.8 kB] 96s Get:82 http://ftpmaster.internal/ubuntu plucky/main armhf libnpth0t64 armhf 1.8-2 [7572 B] 96s Get:83 http://ftpmaster.internal/ubuntu plucky/main armhf gpg-wks-client armhf 2.4.4-2ubuntu22 [87.5 kB] 96s Get:84 http://ftpmaster.internal/ubuntu plucky/main armhf dirmngr armhf 2.4.4-2ubuntu22 [347 kB] 96s Get:85 http://ftpmaster.internal/ubuntu plucky/main armhf gpgsm armhf 2.4.4-2ubuntu22 [242 kB] 96s Get:86 http://ftpmaster.internal/ubuntu plucky/main armhf gnupg-utils armhf 2.4.4-2ubuntu22 [159 kB] 96s Get:87 http://ftpmaster.internal/ubuntu plucky/main armhf gpg-agent armhf 2.4.4-2ubuntu22 [237 kB] 96s Get:88 http://ftpmaster.internal/ubuntu plucky/main armhf gpg armhf 2.4.4-2ubuntu22 [525 kB] 96s Get:89 http://ftpmaster.internal/ubuntu plucky/main armhf gpgconf armhf 2.4.4-2ubuntu22 [116 kB] 96s Get:90 http://ftpmaster.internal/ubuntu plucky/main armhf gnupg all 2.4.4-2ubuntu22 [359 kB] 96s Get:91 http://ftpmaster.internal/ubuntu plucky/main armhf keyboxd armhf 2.4.4-2ubuntu22 [111 kB] 96s Get:92 http://ftpmaster.internal/ubuntu plucky/main armhf pinentry-curses armhf 1.3.1-2ubuntu2 [40.6 kB] 96s Get:93 http://ftpmaster.internal/ubuntu plucky/main armhf libnettle8t64 armhf 3.10.1-1 [188 kB] 96s Get:94 http://ftpmaster.internal/ubuntu plucky/main armhf libhogweed6t64 armhf 3.10.1-1 [188 kB] 96s Get:95 http://ftpmaster.internal/ubuntu plucky/main armhf libffi8 armhf 3.4.7-1 [21.1 kB] 96s Get:96 http://ftpmaster.internal/ubuntu plucky/main armhf libp11-kit0 armhf 0.25.5-2ubuntu3 [261 kB] 96s Get:97 http://ftpmaster.internal/ubuntu plucky/main armhf libtasn1-6 armhf 4.20.0-2 [38.2 kB] 96s Get:98 http://ftpmaster.internal/ubuntu plucky/main armhf libunistring5 armhf 1.3-1 [583 kB] 96s Get:99 http://ftpmaster.internal/ubuntu plucky/main armhf libgnutls30t64 armhf 3.8.9-2ubuntu2 [961 kB] 96s Get:100 http://ftpmaster.internal/ubuntu plucky/main armhf libsasl2-modules-db armhf 2.1.28+dfsg1-8build1 [19.0 kB] 96s Get:101 http://ftpmaster.internal/ubuntu plucky/main armhf libsasl2-2 armhf 2.1.28+dfsg1-8build1 [49.9 kB] 96s Get:102 http://ftpmaster.internal/ubuntu plucky/main armhf libldap-common all 2.6.9+dfsg-1~exp2ubuntu1 [33.2 kB] 96s Get:103 http://ftpmaster.internal/ubuntu plucky/main armhf libldap2 armhf 2.6.9+dfsg-1~exp2ubuntu1 [177 kB] 96s Get:104 http://ftpmaster.internal/ubuntu plucky/main armhf gpgv armhf 2.4.4-2ubuntu22 [225 kB] 96s Get:105 http://ftpmaster.internal/ubuntu plucky/main armhf e2fsprogs-l10n all 1.47.2-1ubuntu1 [7030 B] 96s Get:106 http://ftpmaster.internal/ubuntu plucky/main armhf logsave armhf 1.47.2-1ubuntu1 [25.7 kB] 96s Get:107 http://ftpmaster.internal/ubuntu plucky/main armhf ubuntu-minimal armhf 1.547 [11.4 kB] 96s Get:108 http://ftpmaster.internal/ubuntu plucky/main armhf initramfs-tools all 0.145ubuntu2 [7948 B] 96s Get:109 http://ftpmaster.internal/ubuntu plucky/main armhf initramfs-tools-core all 0.145ubuntu2 [51.5 kB] 96s Get:110 http://ftpmaster.internal/ubuntu plucky/main armhf libext2fs2t64 armhf 1.47.2-1ubuntu1 [207 kB] 96s Get:111 http://ftpmaster.internal/ubuntu plucky/main armhf e2fsprogs armhf 1.47.2-1ubuntu1 [588 kB] 97s Get:112 http://ftpmaster.internal/ubuntu plucky/main armhf dhcpcd-base armhf 1:10.1.0-7 [188 kB] 97s Get:113 http://ftpmaster.internal/ubuntu plucky/main armhf init armhf 1.68 [6296 B] 97s Get:114 http://ftpmaster.internal/ubuntu plucky/main armhf libbpf1 armhf 1:1.5.0-2 [158 kB] 97s Get:115 http://ftpmaster.internal/ubuntu plucky/main armhf iptables armhf 1.8.11-2ubuntu1 [342 kB] 97s Get:116 http://ftpmaster.internal/ubuntu plucky/main armhf libip4tc2 armhf 1.8.11-2ubuntu1 [21.7 kB] 97s Get:117 http://ftpmaster.internal/ubuntu plucky/main armhf libip6tc2 armhf 1.8.11-2ubuntu1 [22.1 kB] 97s Get:118 http://ftpmaster.internal/ubuntu plucky/main armhf libnftnl11 armhf 1.2.8-1 [53.3 kB] 97s Get:119 http://ftpmaster.internal/ubuntu plucky/main armhf libxtables12 armhf 1.8.11-2ubuntu1 [33.0 kB] 97s Get:120 http://ftpmaster.internal/ubuntu plucky/main armhf iproute2 armhf 6.13.0-1ubuntu1 [1096 kB] 97s Get:121 http://ftpmaster.internal/ubuntu plucky/main armhf iputils-ping armhf 3:20240905-1ubuntu1 [45.0 kB] 97s Get:122 http://ftpmaster.internal/ubuntu plucky/main armhf locales all 2.40-4ubuntu1 [4224 kB] 97s Get:123 http://ftpmaster.internal/ubuntu plucky/main armhf login.defs all 1:4.16.0-7ubuntu1 [38.5 kB] 97s Get:124 http://ftpmaster.internal/ubuntu plucky/main armhf login armhf 1:4.16.0-2+really2.40.2-14ubuntu1 [85.0 kB] 97s Get:125 http://ftpmaster.internal/ubuntu plucky/main armhf mawk armhf 1.3.4.20250131-1 [119 kB] 97s Get:126 http://ftpmaster.internal/ubuntu plucky/main armhf netcat-openbsd armhf 1.228-1 [42.4 kB] 97s Get:127 http://ftpmaster.internal/ubuntu plucky/main armhf libpython3.13-minimal armhf 3.13.2-1 [868 kB] 97s Get:128 http://ftpmaster.internal/ubuntu plucky/main armhf python3.13-minimal armhf 3.13.2-1 [2012 kB] 97s Get:129 http://ftpmaster.internal/ubuntu plucky/main armhf python3-cryptography armhf 43.0.0-1 [925 kB] 97s Get:130 http://ftpmaster.internal/ubuntu plucky/main armhf python3-minimal armhf 3.13.1-1~exp2 [27.6 kB] 97s Get:131 http://ftpmaster.internal/ubuntu plucky/main armhf python3 armhf 3.13.1-1~exp2 [23.9 kB] 97s Get:132 http://ftpmaster.internal/ubuntu plucky/main armhf python3-bcrypt armhf 4.2.0-2.1 [239 kB] 97s Get:133 http://ftpmaster.internal/ubuntu plucky/main armhf tzdata all 2025a-2ubuntu1 [198 kB] 97s Get:134 http://ftpmaster.internal/ubuntu plucky/main armhf libpython3.13-stdlib armhf 3.13.2-1 [1969 kB] 97s Get:135 http://ftpmaster.internal/ubuntu plucky/main armhf python3.13 armhf 3.13.2-1 [734 kB] 97s Get:136 http://ftpmaster.internal/ubuntu plucky/main armhf libpython3-stdlib armhf 3.13.1-1~exp2 [10.2 kB] 97s Get:137 http://ftpmaster.internal/ubuntu plucky/main armhf gir1.2-girepository-2.0 armhf 1.82.0-4 [25.3 kB] 97s Get:138 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf gir1.2-glib-2.0 armhf 2.83.4-1 [185 kB] 97s Get:139 http://ftpmaster.internal/ubuntu plucky/main armhf libgirepository-1.0-1 armhf 1.82.0-4 [109 kB] 97s Get:140 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf libglib2.0-data all 2.83.4-1 [52.9 kB] 97s Get:141 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf libglib2.0-bin armhf 2.83.4-1 [92.7 kB] 97s Get:142 http://ftpmaster.internal/ubuntu plucky/main armhf libatomic1 armhf 15-20250213-1ubuntu1 [7938 B] 97s Get:143 http://ftpmaster.internal/ubuntu plucky-proposed/main armhf libglib2.0-0t64 armhf 2.83.4-1 [1453 kB] 97s Get:144 http://ftpmaster.internal/ubuntu plucky/main armhf netplan-generator armhf 1.1.2-2ubuntu1 [60.8 kB] 97s Get:145 http://ftpmaster.internal/ubuntu plucky/main armhf libyaml-0-2 armhf 0.2.5-2 [45.3 kB] 97s Get:146 http://ftpmaster.internal/ubuntu plucky/main armhf python3-netplan armhf 1.1.2-2ubuntu1 [24.2 kB] 97s Get:147 http://ftpmaster.internal/ubuntu plucky/main armhf netplan.io armhf 1.1.2-2ubuntu1 [67.7 kB] 97s Get:148 http://ftpmaster.internal/ubuntu plucky/main armhf libnetplan1 armhf 1.1.2-2ubuntu1 [123 kB] 97s Get:149 http://ftpmaster.internal/ubuntu plucky/main armhf ethtool armhf 1:6.11-1 [222 kB] 97s Get:150 http://ftpmaster.internal/ubuntu plucky/main armhf libsemanage-common all 3.7-2.1 [7198 B] 97s Get:151 http://ftpmaster.internal/ubuntu plucky/main armhf libsemanage2 armhf 3.7-2.1 [85.4 kB] 97s Get:152 http://ftpmaster.internal/ubuntu plucky/main armhf passwd armhf 1:4.16.0-7ubuntu1 [1041 kB] 97s Get:153 http://ftpmaster.internal/ubuntu plucky/main armhf ubuntu-pro-client-l10n armhf 34.1.3 [18.3 kB] 97s Get:154 http://ftpmaster.internal/ubuntu plucky/main armhf python-apt-common all 2.9.9 [21.2 kB] 97s Get:155 http://ftpmaster.internal/ubuntu plucky/main armhf python3-apt armhf 2.9.9 [173 kB] 97s Get:156 http://ftpmaster.internal/ubuntu plucky/main armhf distro-info armhf 1.13 [19.1 kB] 97s Get:157 http://ftpmaster.internal/ubuntu plucky/main armhf ubuntu-pro-client armhf 34.1.3 [243 kB] 97s Get:158 http://ftpmaster.internal/ubuntu plucky/main armhf vim-tiny armhf 2:9.1.0967-1ubuntu2 [696 kB] 97s Get:159 http://ftpmaster.internal/ubuntu plucky/main armhf vim-common all 2:9.1.0967-1ubuntu2 [396 kB] 97s Get:160 http://ftpmaster.internal/ubuntu plucky/main armhf python3-newt armhf 0.52.24-4ubuntu1 [20.1 kB] 97s Get:161 http://ftpmaster.internal/ubuntu plucky/main armhf libnewt0.52 armhf 0.52.24-4ubuntu1 [39.7 kB] 97s Get:162 http://ftpmaster.internal/ubuntu plucky/main armhf whiptail armhf 0.52.24-4ubuntu1 [17.3 kB] 97s Get:163 http://ftpmaster.internal/ubuntu plucky/main armhf dracut-install armhf 106-2ubuntu1 [38.7 kB] 97s Get:164 http://ftpmaster.internal/ubuntu plucky/main armhf initramfs-tools-bin armhf 0.145ubuntu2 [24.5 kB] 97s Get:165 http://ftpmaster.internal/ubuntu plucky/main armhf busybox-initramfs armhf 1:1.37.0-4ubuntu1 [188 kB] 97s Get:166 http://ftpmaster.internal/ubuntu plucky/main armhf python3.12 armhf 3.12.9-1 [671 kB] 97s Get:167 http://ftpmaster.internal/ubuntu plucky/main armhf libpython3.12-stdlib armhf 3.12.9-1 [1946 kB] 97s Get:168 http://ftpmaster.internal/ubuntu plucky/main armhf python3.12-minimal armhf 3.12.9-1 [2012 kB] 97s Get:169 http://ftpmaster.internal/ubuntu plucky/main armhf libpython3.12-minimal armhf 3.12.9-1 [825 kB] 97s Get:170 http://ftpmaster.internal/ubuntu plucky/main armhf cron armhf 3.0pl1-192ubuntu1 [84.2 kB] 97s Get:171 http://ftpmaster.internal/ubuntu plucky/main armhf rsync armhf 3.4.1-0syncable1 [422 kB] 97s Get:172 http://ftpmaster.internal/ubuntu plucky/main armhf python3-lazr.uri all 1.0.6-5 [13.6 kB] 97s Get:173 http://ftpmaster.internal/ubuntu plucky/main armhf python3-launchpadlib all 2.1.0-1 [126 kB] 97s Get:174 http://ftpmaster.internal/ubuntu plucky/main armhf python3-problem-report all 2.31.0+git20250220-0ubuntu1 [26.0 kB] 97s Get:175 http://ftpmaster.internal/ubuntu plucky/main armhf python3-apport all 2.31.0+git20250220-0ubuntu1 [93.5 kB] 97s Get:176 http://ftpmaster.internal/ubuntu plucky/main armhf python3-gi armhf 3.50.0-4 [260 kB] 97s Get:177 http://ftpmaster.internal/ubuntu plucky/main armhf apport-core-dump-handler all 2.31.0+git20250220-0ubuntu1 [18.7 kB] 98s Get:178 http://ftpmaster.internal/ubuntu plucky/main armhf apport all 2.31.0+git20250220-0ubuntu1 [83.1 kB] 98s Get:179 http://ftpmaster.internal/ubuntu plucky/main armhf gcc-14-base armhf 14.2.0-17ubuntu3 [53.6 kB] 98s Get:180 http://ftpmaster.internal/ubuntu plucky/main armhf libcom-err2 armhf 1.47.2-1ubuntu1 [25.6 kB] 98s Get:181 http://ftpmaster.internal/ubuntu plucky/main armhf libss2 armhf 1.47.2-1ubuntu1 [15.6 kB] 98s Get:182 http://ftpmaster.internal/ubuntu plucky/main armhf openssl armhf 3.4.1-1ubuntu1 [1152 kB] 98s Get:183 http://ftpmaster.internal/ubuntu plucky/main armhf ca-certificates all 20241223 [165 kB] 98s Get:184 http://ftpmaster.internal/ubuntu plucky/main armhf krb5-locales all 1.21.3-4ubuntu1 [14.7 kB] 98s Get:185 http://ftpmaster.internal/ubuntu plucky/main armhf libfribidi0 armhf 1.0.16-1 [24.3 kB] 98s Get:186 http://ftpmaster.internal/ubuntu plucky/main armhf libgssapi-krb5-2 armhf 1.21.3-4ubuntu1 [121 kB] 98s Get:187 http://ftpmaster.internal/ubuntu plucky/main armhf libkrb5-3 armhf 1.21.3-4ubuntu1 [314 kB] 98s Get:188 http://ftpmaster.internal/ubuntu plucky/main armhf libkrb5support0 armhf 1.21.3-4ubuntu1 [31.8 kB] 98s Get:189 http://ftpmaster.internal/ubuntu plucky/main armhf libk5crypto3 armhf 1.21.3-4ubuntu1 [78.6 kB] 98s Get:190 http://ftpmaster.internal/ubuntu plucky/main armhf libicu74 armhf 74.2-1ubuntu6 [10.5 MB] 98s Get:191 http://ftpmaster.internal/ubuntu plucky/main armhf libxml2 armhf 2.12.7+dfsg+really2.9.14-0.2ubuntu3 [599 kB] 98s Get:192 http://ftpmaster.internal/ubuntu plucky/main armhf python3-pygments all 2.18.0+dfsg-2 [835 kB] 98s Get:193 http://ftpmaster.internal/ubuntu plucky/main armhf python3-rich all 13.9.4-1 [190 kB] 98s Get:194 http://ftpmaster.internal/ubuntu plucky/main armhf ucf all 3.0050 [43.5 kB] 98s Get:195 http://ftpmaster.internal/ubuntu plucky/main armhf rsyslog armhf 8.2412.0-2ubuntu1 [471 kB] 98s Get:196 http://ftpmaster.internal/ubuntu plucky/main armhf xxd armhf 2:9.1.0967-1ubuntu2 [67.5 kB] 98s Get:197 http://ftpmaster.internal/ubuntu plucky/main armhf apparmor armhf 4.1.0~beta5-0ubuntu5 [605 kB] 98s Get:198 http://ftpmaster.internal/ubuntu plucky/main armhf bash-completion all 1:2.16.0-7 [214 kB] 98s Get:199 http://ftpmaster.internal/ubuntu plucky/main armhf libjemalloc2 armhf 5.3.0-2build1 [200 kB] 98s Get:200 http://ftpmaster.internal/ubuntu plucky/main armhf libmaxminddb0 armhf 1.12.2-1 [16.9 kB] 98s Get:201 http://ftpmaster.internal/ubuntu plucky/main armhf liburcu8t64 armhf 0.15.1-1 [57.1 kB] 98s Get:202 http://ftpmaster.internal/ubuntu plucky/main armhf bind9-dnsutils armhf 1:9.20.4-3ubuntu1 [155 kB] 98s Get:203 http://ftpmaster.internal/ubuntu plucky/main armhf bind9-host armhf 1:9.20.4-3ubuntu1 [46.4 kB] 98s Get:204 http://ftpmaster.internal/ubuntu plucky/main armhf bind9-libs armhf 1:9.20.4-3ubuntu1 [1186 kB] 99s Get:205 http://ftpmaster.internal/ubuntu plucky/main armhf libedit2 armhf 3.1-20250104-1 [79.3 kB] 99s Get:206 http://ftpmaster.internal/ubuntu plucky/main armhf busybox-static armhf 1:1.37.0-4ubuntu1 [857 kB] 99s Get:207 http://ftpmaster.internal/ubuntu plucky/main armhf cron-daemon-common all 3.0pl1-192ubuntu1 [14.5 kB] 99s Get:208 http://ftpmaster.internal/ubuntu plucky/main armhf dmsetup armhf 2:1.02.201-1ubuntu1 [80.4 kB] 99s Get:209 http://ftpmaster.internal/ubuntu plucky/main armhf ed armhf 1.21-1 [52.8 kB] 99s Get:210 http://ftpmaster.internal/ubuntu plucky/main armhf gettext-base armhf 0.23.1-1 [43.3 kB] 99s Get:211 http://ftpmaster.internal/ubuntu plucky/main armhf groff-base armhf 1.23.0-7 [949 kB] 99s Get:212 http://ftpmaster.internal/ubuntu plucky/main armhf libibverbs1 armhf 55.0-1ubuntu1 [58.5 kB] 99s Get:213 http://ftpmaster.internal/ubuntu plucky/main armhf ibverbs-providers armhf 55.0-1ubuntu1 [27.6 kB] 99s Get:214 http://ftpmaster.internal/ubuntu plucky/main armhf inetutils-telnet armhf 2:2.5-6ubuntu1 [94.7 kB] 99s Get:215 http://ftpmaster.internal/ubuntu plucky/main armhf iputils-tracepath armhf 3:20240905-1ubuntu1 [13.3 kB] 99s Get:216 http://ftpmaster.internal/ubuntu plucky/main armhf libcbor0.10 armhf 0.10.2-2ubuntu1 [22.0 kB] 99s Get:217 http://ftpmaster.internal/ubuntu plucky/main armhf nftables armhf 1.1.1-1build1 [70.8 kB] 99s Get:218 http://ftpmaster.internal/ubuntu plucky/main armhf libnftables1 armhf 1.1.1-1build1 [321 kB] 99s Get:219 http://ftpmaster.internal/ubuntu plucky/main armhf libpcap0.8t64 armhf 1.10.5-2ubuntu1 [140 kB] 99s Get:220 http://ftpmaster.internal/ubuntu plucky/main armhf libpng16-16t64 armhf 1.6.46-4 [171 kB] 99s Get:221 http://ftpmaster.internal/ubuntu plucky/main armhf libxkbcommon0 armhf 1.7.0-2 [113 kB] 99s Get:222 http://ftpmaster.internal/ubuntu plucky/main armhf libplymouth5 armhf 24.004.60-2ubuntu5 [142 kB] 99s Get:223 http://ftpmaster.internal/ubuntu plucky/main armhf libtraceevent1-plugin armhf 1:1.8.4-2 [19.0 kB] 99s Get:224 http://ftpmaster.internal/ubuntu plucky/main armhf libtraceevent1 armhf 1:1.8.4-2 [53.8 kB] 99s Get:225 http://ftpmaster.internal/ubuntu plucky/main armhf libusb-1.0-0 armhf 2:1.0.27-2 [49.5 kB] 99s Get:226 http://ftpmaster.internal/ubuntu plucky/main armhf libxdmcp6 armhf 1:1.1.5-1 [9060 B] 99s Get:227 http://ftpmaster.internal/ubuntu plucky/main armhf lshw armhf 02.19.git.2021.06.19.996aaad9c7-2.1ubuntu1 [311 kB] 99s Get:228 http://ftpmaster.internal/ubuntu plucky/main armhf lsof armhf 4.99.4+dfsg-2 [239 kB] 99s Get:229 http://ftpmaster.internal/ubuntu plucky/main armhf liblsof0 armhf 4.99.4+dfsg-2 [60.8 kB] 99s Get:230 http://ftpmaster.internal/ubuntu plucky/main armhf nano armhf 8.3-1 [277 kB] 99s Get:231 http://ftpmaster.internal/ubuntu plucky/main armhf pci.ids all 0.0~2025.02.12-1 [284 kB] 99s Get:232 http://ftpmaster.internal/ubuntu plucky/main armhf plymouth-theme-ubuntu-text armhf 24.004.60-2ubuntu5 [9914 B] 99s Get:233 http://ftpmaster.internal/ubuntu plucky/main armhf libpackagekit-glib2-18 armhf 1.3.0-3build1 [109 kB] 99s Get:234 http://ftpmaster.internal/ubuntu plucky/main armhf packagekit-tools armhf 1.3.0-3build1 [28.0 kB] 99s Get:235 http://ftpmaster.internal/ubuntu plucky/main armhf polkitd armhf 126-2 [92.5 kB] 99s Get:236 http://ftpmaster.internal/ubuntu plucky/main armhf libpolkit-agent-1-0 armhf 126-2 [15.1 kB] 99s Get:237 http://ftpmaster.internal/ubuntu plucky/main armhf libpolkit-gobject-1-0 armhf 126-2 [45.0 kB] 99s Get:238 http://ftpmaster.internal/ubuntu plucky/main armhf libcurl3t64-gnutls armhf 8.12.0+git20250209.89ed161+ds-1ubuntu1 [330 kB] 99s Get:239 http://ftpmaster.internal/ubuntu plucky/main armhf libappstream5 armhf 1.0.4-1 [211 kB] 99s Get:240 http://ftpmaster.internal/ubuntu plucky/main armhf libgstreamer1.0-0 armhf 1.25.50-1 [1164 kB] 99s Get:241 http://ftpmaster.internal/ubuntu plucky/main armhf packagekit armhf 1.3.0-3build1 [431 kB] 99s Get:242 http://ftpmaster.internal/ubuntu plucky/main armhf plymouth armhf 24.004.60-2ubuntu5 [143 kB] 99s Get:243 http://ftpmaster.internal/ubuntu plucky/main armhf powermgmt-base all 1.38 [7378 B] 99s Get:244 http://ftpmaster.internal/ubuntu plucky/main armhf psmisc armhf 23.7-2 [177 kB] 99s Get:245 http://ftpmaster.internal/ubuntu plucky/main armhf publicsuffix all 20250108.1153-0.1 [134 kB] 99s Get:246 http://ftpmaster.internal/ubuntu plucky/main armhf python3-distro-info all 1.13 [7798 B] 99s Get:247 http://ftpmaster.internal/ubuntu plucky/main armhf python3.13-gdbm armhf 3.13.2-1 [30.2 kB] 99s Get:248 http://ftpmaster.internal/ubuntu plucky/main armhf python3.12-gdbm armhf 3.12.9-1 [29.3 kB] 99s Get:249 http://ftpmaster.internal/ubuntu plucky/main armhf python3-gdbm armhf 3.13.1-1 [8668 B] 99s Get:250 http://ftpmaster.internal/ubuntu plucky/main armhf telnet all 0.17+2.5-6ubuntu1 [3694 B] 99s Get:251 http://ftpmaster.internal/ubuntu plucky/main armhf ubuntu-standard armhf 1.547 [11.4 kB] 99s Get:252 http://ftpmaster.internal/ubuntu plucky/main armhf ufw all 0.36.2-9 [170 kB] 99s Get:253 http://ftpmaster.internal/ubuntu plucky/main armhf usb.ids all 2025.01.14-1 [223 kB] 99s Get:254 http://ftpmaster.internal/ubuntu plucky/main armhf xauth armhf 1:1.1.2-1.1 [23.0 kB] 99s Get:255 http://ftpmaster.internal/ubuntu plucky/main armhf appstream armhf 1.0.4-1 [67.3 kB] 99s Get:256 http://ftpmaster.internal/ubuntu plucky/main armhf libctf0 armhf 2.44-2ubuntu1 [74.3 kB] 99s Get:257 http://ftpmaster.internal/ubuntu plucky/main armhf libctf-nobfd0 armhf 2.44-2ubuntu1 [77.6 kB] 99s Get:258 http://ftpmaster.internal/ubuntu plucky/main armhf binutils-arm-linux-gnueabihf armhf 2.44-2ubuntu1 [995 kB] 99s Get:259 http://ftpmaster.internal/ubuntu plucky/main armhf libbinutils armhf 2.44-2ubuntu1 [405 kB] 99s Get:260 http://ftpmaster.internal/ubuntu plucky/main armhf binutils armhf 2.44-2ubuntu1 [3234 B] 99s Get:261 http://ftpmaster.internal/ubuntu plucky/main armhf binutils-common armhf 2.44-2ubuntu1 [215 kB] 99s Get:262 http://ftpmaster.internal/ubuntu plucky/main armhf libsframe1 armhf 2.44-2ubuntu1 [12.4 kB] 99s Get:263 http://ftpmaster.internal/ubuntu plucky/main armhf btrfs-progs armhf 6.12-1build1 [884 kB] 99s Get:264 http://ftpmaster.internal/ubuntu plucky/main armhf python3-certifi all 2025.1.31+ds-1 [9816 B] 99s Get:265 http://ftpmaster.internal/ubuntu plucky/main armhf python3-chardet all 5.2.0+dfsg-2 [116 kB] 99s Get:266 http://ftpmaster.internal/ubuntu plucky/main armhf python3-idna all 3.10-1 [47.4 kB] 100s Get:267 http://ftpmaster.internal/ubuntu plucky/main armhf python3-urllib3 all 2.3.0-1 [94.0 kB] 100s Get:268 http://ftpmaster.internal/ubuntu plucky/main armhf python3-requests all 2.32.3+dfsg-4ubuntu1 [52.9 kB] 100s Get:269 http://ftpmaster.internal/ubuntu plucky/main armhf python3-jinja2 all 3.1.5-2 [109 kB] 100s Get:270 http://ftpmaster.internal/ubuntu plucky/main armhf python3-json-pointer all 2.4-3 [8444 B] 100s Get:271 http://ftpmaster.internal/ubuntu plucky/main armhf python3-jsonpatch all 1.32-5 [12.3 kB] 100s Get:272 http://ftpmaster.internal/ubuntu plucky/main armhf python3-attr all 25.1.0-1 [50.4 kB] 100s Get:273 http://ftpmaster.internal/ubuntu plucky/main armhf python3-referencing all 0.35.1-2ubuntu1 [21.9 kB] 100s Get:274 http://ftpmaster.internal/ubuntu plucky/main armhf python3-jsonschema all 4.19.2-6ubuntu1 [65.5 kB] 100s Get:275 http://ftpmaster.internal/ubuntu plucky/main armhf python3-jwt all 2.10.1-2 [21.0 kB] 100s Get:276 http://ftpmaster.internal/ubuntu plucky/main armhf python3-oauthlib all 3.2.2-3 [89.9 kB] 100s Get:277 http://ftpmaster.internal/ubuntu plucky/main armhf cloud-init-base all 25.1-0ubuntu1 [616 kB] 100s Get:278 http://ftpmaster.internal/ubuntu plucky/main armhf cryptsetup-bin armhf 2:2.7.5-1ubuntu2 [220 kB] 100s Get:279 http://ftpmaster.internal/ubuntu plucky/main armhf curl armhf 8.12.0+git20250209.89ed161+ds-1ubuntu1 [247 kB] 100s Get:280 http://ftpmaster.internal/ubuntu plucky/main armhf libcurl4t64 armhf 8.12.0+git20250209.89ed161+ds-1ubuntu1 [335 kB] 100s Get:281 http://ftpmaster.internal/ubuntu plucky/main armhf dpkg-dev all 1.22.11ubuntu4 [1088 kB] 100s Get:282 http://ftpmaster.internal/ubuntu plucky/main armhf libdpkg-perl all 1.22.11ubuntu4 [279 kB] 100s Get:283 http://ftpmaster.internal/ubuntu plucky/main armhf make armhf 4.4.1-1 [180 kB] 100s Get:284 http://ftpmaster.internal/ubuntu plucky/main armhf lto-disabled-list all 56 [12.4 kB] 100s Get:285 http://ftpmaster.internal/ubuntu plucky/main armhf libarchive13t64 armhf 3.7.7-0ubuntu1 [335 kB] 100s Get:286 http://ftpmaster.internal/ubuntu plucky/main armhf libjson-glib-1.0-common all 1.10.6+ds-1 [5636 B] 100s Get:287 http://ftpmaster.internal/ubuntu plucky/main armhf libjson-glib-1.0-0 armhf 1.10.6+ds-1 [59.5 kB] 100s Get:288 http://ftpmaster.internal/ubuntu plucky/main armhf fwupd armhf 2.0.6-3 [5155 kB] 100s Get:289 http://ftpmaster.internal/ubuntu plucky/main armhf libfwupd3 armhf 2.0.6-3 [125 kB] 100s Get:290 http://ftpmaster.internal/ubuntu plucky/main armhf libprotobuf-c1 armhf 1.5.1-1ubuntu1 [18.1 kB] 100s Get:291 http://ftpmaster.internal/ubuntu plucky/main armhf libqmi-proxy armhf 1.35.6-1 [5878 B] 100s Get:292 http://ftpmaster.internal/ubuntu plucky/main armhf libqmi-glib5 armhf 1.35.6-1 [928 kB] 100s Get:293 http://ftpmaster.internal/ubuntu plucky/main armhf gir1.2-packagekitglib-1.0 armhf 1.3.0-3build1 [25.5 kB] 100s Get:294 http://ftpmaster.internal/ubuntu plucky/main armhf gnupg-l10n all 2.4.4-2ubuntu22 [66.4 kB] 100s Get:295 http://ftpmaster.internal/ubuntu plucky/main armhf htop armhf 3.3.0-5 [140 kB] 100s Get:296 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-utils3 armhf 3.3.0-1 [17.5 kB] 100s Get:297 http://ftpmaster.internal/ubuntu plucky/main armhf libnspr4 armhf 2:4.36-1ubuntu1 [94.5 kB] 100s Get:298 http://ftpmaster.internal/ubuntu plucky/main armhf libnss3 armhf 2:3.108-1ubuntu1 [1317 kB] 100s Get:299 http://ftpmaster.internal/ubuntu plucky/main armhf libgpgme11t64 armhf 1.24.2-1ubuntu1 [125 kB] 100s Get:300 http://ftpmaster.internal/ubuntu plucky/main armhf libvolume-key1 armhf 0.3.12-9 [39.1 kB] 100s Get:301 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-crypto3 armhf 3.3.0-1 [22.4 kB] 100s Get:302 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-fs3 armhf 3.3.0-1 [34.5 kB] 101s Get:303 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-loop3 armhf 3.3.0-1 [6594 B] 101s Get:304 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-mdraid3 armhf 3.3.0-1 [13.4 kB] 101s Get:305 http://ftpmaster.internal/ubuntu plucky/main armhf libnvme1t64 armhf 1.11.1-2 [73.6 kB] 101s Get:306 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-nvme3 armhf 3.3.0-1 [17.7 kB] 101s Get:307 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-part3 armhf 3.3.0-1 [16.6 kB] 101s Get:308 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev-swap3 armhf 3.3.0-1 [9010 B] 101s Get:309 http://ftpmaster.internal/ubuntu plucky/main armhf libblockdev3 armhf 3.3.0-1 [44.4 kB] 101s Get:310 http://ftpmaster.internal/ubuntu plucky/main armhf libftdi1-2 armhf 1.5-8 [26.3 kB] 101s Get:311 http://ftpmaster.internal/ubuntu plucky/main armhf libgudev-1.0-0 armhf 1:238-6 [13.7 kB] 101s Get:312 http://ftpmaster.internal/ubuntu plucky/main armhf libicu76 armhf 76.1-1ubuntu2 [10.8 MB] 102s Get:313 http://ftpmaster.internal/ubuntu plucky/main armhf libsasl2-modules armhf 2.1.28+dfsg1-8build1 [62.7 kB] 102s Get:314 http://ftpmaster.internal/ubuntu plucky/main armhf udisks2 armhf 2.10.1-11ubuntu2 [278 kB] 102s Get:315 http://ftpmaster.internal/ubuntu plucky/main armhf libudisks2-0 armhf 2.10.1-11ubuntu2 [142 kB] 102s Get:316 http://ftpmaster.internal/ubuntu plucky/main armhf libwrap0 armhf 7.6.q-35 [45.6 kB] 102s Get:317 http://ftpmaster.internal/ubuntu plucky/main armhf linux-headers-6.12.0-15 all 6.12.0-15.15 [14.1 MB] 103s Get:318 http://ftpmaster.internal/ubuntu plucky/main armhf linux-headers-6.12.0-15-generic armhf 6.12.0-15.15 [1414 kB] 103s Get:319 http://ftpmaster.internal/ubuntu plucky/main armhf linux-headers-generic armhf 6.12.0-15.15+1 [10.8 kB] 103s Get:320 http://ftpmaster.internal/ubuntu plucky/main armhf pollinate all 4.33-4ubuntu2 [12.4 kB] 103s Get:321 http://ftpmaster.internal/ubuntu plucky/main armhf python3-babel all 2.17.0-1 [101 kB] 103s Get:322 http://ftpmaster.internal/ubuntu plucky/main armhf python-babel-localedata all 2.17.0-1 [6678 kB] 103s Get:323 http://ftpmaster.internal/ubuntu plucky/main armhf python3-more-itertools all 10.6.0-1 [57.7 kB] 103s Get:324 http://ftpmaster.internal/ubuntu plucky/main armhf python3-openssl all 25.0.0-1 [46.1 kB] 103s Get:325 http://ftpmaster.internal/ubuntu plucky/main armhf python3-pkg-resources all 75.6.0-1 [144 kB] 103s Get:326 http://ftpmaster.internal/ubuntu plucky/main armhf python3-setuptools all 75.6.0-1 [645 kB] 103s Get:327 http://ftpmaster.internal/ubuntu plucky/main armhf software-properties-common all 0.109 [16.5 kB] 103s Get:328 http://ftpmaster.internal/ubuntu plucky/main armhf python3-software-properties all 0.109 [31.0 kB] 103s Get:329 http://ftpmaster.internal/ubuntu plucky/main armhf python3-wadllib all 2.0.0-2 [36.2 kB] 103s Get:330 http://ftpmaster.internal/ubuntu plucky/main armhf tmux armhf 3.5a-3 [406 kB] 103s Get:331 http://ftpmaster.internal/ubuntu plucky/main armhf unattended-upgrades all 2.12ubuntu4 [58.5 kB] 103s Get:332 http://ftpmaster.internal/ubuntu plucky/main armhf xfsprogs armhf 6.12.0-1ubuntu1 [958 kB] 103s Get:333 http://ftpmaster.internal/ubuntu plucky/main armhf zstd armhf 1.5.6+dfsg-2 [690 kB] 103s Get:334 http://ftpmaster.internal/ubuntu plucky/main armhf cloud-init all 25.1-0ubuntu1 [2088 B] 103s Get:335 http://ftpmaster.internal/ubuntu plucky/main armhf kpartx armhf 0.9.9-1ubuntu4 [35.0 kB] 103s Get:336 http://ftpmaster.internal/ubuntu plucky/main armhf multipath-tools armhf 0.9.9-1ubuntu4 [294 kB] 104s Preconfiguring packages ... 106s Fetched 148 MB in 10s (15.5 MB/s) 106s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59970 files and directories currently installed.) 106s Preparing to unpack .../motd-news-config_13.6ubuntu1_all.deb ... 106s Unpacking motd-news-config (13.6ubuntu1) over (13.5ubuntu3) ... 106s Selecting previously unselected package gcc-15-base:armhf. 106s Preparing to unpack .../gcc-15-base_15-20250213-1ubuntu1_armhf.deb ... 106s Unpacking gcc-15-base:armhf (15-20250213-1ubuntu1) ... 106s Setting up gcc-15-base:armhf (15-20250213-1ubuntu1) ... 106s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59975 files and directories currently installed.) 106s Preparing to unpack .../libgcc-s1_15-20250213-1ubuntu1_armhf.deb ... 106s Unpacking libgcc-s1:armhf (15-20250213-1ubuntu1) over (14.2.0-8ubuntu1) ... 106s Setting up libgcc-s1:armhf (15-20250213-1ubuntu1) ... 106s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 59975 files and directories currently installed.) 106s Preparing to unpack .../libc6_2.40-4ubuntu1_armhf.deb ... 106s Unpacking libc6:armhf (2.40-4ubuntu1) over (2.40-1ubuntu3) ... 106s Setting up libc6:armhf (2.40-4ubuntu1) ... 107s (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 ... 59975 files and directories currently installed.) 107s Preparing to unpack .../libcrypt1_1%3a4.4.38-1_armhf.deb ... 107s Unpacking libcrypt1:armhf (1:4.4.38-1) over (1:4.4.36-5) ... 107s Setting up libcrypt1:armhf (1:4.4.38-1) ... 107s (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 ... 59975 files and directories currently installed.) 107s Preparing to unpack .../base-files_13.6ubuntu1_armhf.deb ... 107s Unpacking base-files (13.6ubuntu1) over (13.5ubuntu3) ... 107s Setting up base-files (13.6ubuntu1) ... 107s Updating /root/.profile to current default. 108s motd-news.service is a disabled or a static unit not running, not starting it. 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 ... 59975 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 ... 59975 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 ... 59975 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) ... 108s Setting up coreutils (9.5-1ubuntu1) ... 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 ... 59975 files and directories currently installed.) 108s Preparing to unpack .../dash_0.5.12-12ubuntu1_armhf.deb ... 108s Unpacking dash (0.5.12-12ubuntu1) over (0.5.12-9ubuntu1) ... 108s Setting up dash (0.5.12-12ubuntu1) ... 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 ... 59975 files and directories currently installed.) 108s Preparing to unpack .../diffutils_1%3a3.10-2_armhf.deb ... 108s Unpacking diffutils (1:3.10-2) over (1:3.10-1build1) ... 108s Setting up diffutils (1:3.10-2) ... 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 ... 59975 files and directories currently installed.) 108s Preparing to unpack .../libxxhash0_0.8.3-2_armhf.deb ... 108s Unpacking libxxhash0:armhf (0.8.3-2) over (0.8.2-2build1) ... 108s Setting up libxxhash0:armhf (0.8.3-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 ... 59975 files and directories currently installed.) 109s Preparing to unpack .../liblz4-1_1.10.0-3_armhf.deb ... 109s Unpacking liblz4-1:armhf (1.10.0-3) over (1.9.4-3) ... 109s Setting up liblz4-1:armhf (1.10.0-3) ... 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 ... 59975 files and directories currently installed.) 109s Preparing to unpack .../libssl3t64_3.4.1-1ubuntu1_armhf.deb ... 109s Unpacking libssl3t64:armhf (3.4.1-1ubuntu1) over (3.3.1-2ubuntu2) ... 109s Selecting previously unselected package openssl-provider-legacy. 109s Preparing to unpack .../openssl-provider-legacy_3.4.1-1ubuntu1_armhf.deb ... 109s Unpacking openssl-provider-legacy (3.4.1-1ubuntu1) ... 109s Setting up libssl3t64:armhf (3.4.1-1ubuntu1) ... 109s Setting up openssl-provider-legacy (3.4.1-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 ... 59977 files and directories currently installed.) 109s Preparing to unpack .../libzstd1_1.5.6+dfsg-2_armhf.deb ... 109s Unpacking libzstd1:armhf (1.5.6+dfsg-2) over (1.5.6+dfsg-1) ... 109s Setting up libzstd1:armhf (1.5.6+dfsg-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 ... 59977 files and directories currently installed.) 109s Preparing to unpack .../libstdc++6_15-20250213-1ubuntu1_armhf.deb ... 109s Unpacking libstdc++6:armhf (15-20250213-1ubuntu1) over (14.2.0-8ubuntu1) ... 109s Setting up libstdc++6:armhf (15-20250213-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 ... 59977 files and directories currently installed.) 109s Preparing to unpack .../0-systemd-timesyncd_257.2-3ubuntu1_armhf.deb ... 109s Unpacking systemd-timesyncd (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 109s Preparing to unpack .../1-dbus-session-bus-common_1.16.0-1ubuntu1_all.deb ... 109s Unpacking dbus-session-bus-common (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 109s Preparing to unpack .../2-systemd-sysv_257.2-3ubuntu1_armhf.deb ... 109s Unpacking systemd-sysv (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 109s Preparing to unpack .../3-libpam-systemd_257.2-3ubuntu1_armhf.deb ... 109s Unpacking libpam-systemd:armhf (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 109s Preparing to unpack .../4-dbus-user-session_1.16.0-1ubuntu1_armhf.deb ... 109s Unpacking dbus-user-session (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 109s Preparing to unpack .../5-libapparmor1_4.1.0~beta5-0ubuntu5_armhf.deb ... 109s Unpacking libapparmor1:armhf (4.1.0~beta5-0ubuntu5) over (4.1.0~beta1-0ubuntu4) ... 109s Preparing to unpack .../6-libcap-ng0_0.8.5-4_armhf.deb ... 109s Unpacking libcap-ng0:armhf (0.8.5-4) over (0.8.5-3build1) ... 109s Setting up libcap-ng0:armhf (0.8.5-4) ... 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 ... 59978 files and directories currently installed.) 109s Preparing to unpack .../libselinux1_3.7-3ubuntu2_armhf.deb ... 109s Unpacking libselinux1:armhf (3.7-3ubuntu2) over (3.7-3ubuntu1) ... 110s Setting up libselinux1:armhf (3.7-3ubuntu2) ... 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 ... 59978 files and directories currently installed.) 110s Preparing to unpack .../0-dbus-system-bus-common_1.16.0-1ubuntu1_all.deb ... 110s Unpacking dbus-system-bus-common (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 110s Preparing to unpack .../1-dbus-bin_1.16.0-1ubuntu1_armhf.deb ... 110s Unpacking dbus-bin (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 110s Preparing to unpack .../2-dbus_1.16.0-1ubuntu1_armhf.deb ... 110s Unpacking dbus (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 110s Preparing to unpack .../3-dbus-daemon_1.16.0-1ubuntu1_armhf.deb ... 110s Unpacking dbus-daemon (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 110s Preparing to unpack .../4-libdbus-1-3_1.16.0-1ubuntu1_armhf.deb ... 110s Unpacking libdbus-1-3:armhf (1.16.0-1ubuntu1) over (1.14.10-4ubuntu5) ... 110s Preparing to unpack .../5-systemd-resolved_257.2-3ubuntu1_armhf.deb ... 110s Unpacking systemd-resolved (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 110s Preparing to unpack .../6-libncurses6_6.5+20250125-2_armhf.deb ... 110s Unpacking libncurses6:armhf (6.5+20250125-2) over (6.5-2) ... 110s Preparing to unpack .../7-libncursesw6_6.5+20250125-2_armhf.deb ... 110s Unpacking libncursesw6:armhf (6.5+20250125-2) over (6.5-2) ... 110s Preparing to unpack .../8-libtinfo6_6.5+20250125-2_armhf.deb ... 110s Unpacking libtinfo6:armhf (6.5+20250125-2) over (6.5-2) ... 110s Setting up libtinfo6:armhf (6.5+20250125-2) ... 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 ... 59978 files and directories currently installed.) 110s Preparing to unpack .../bsdextrautils_2.40.2-14ubuntu1_armhf.deb ... 110s Unpacking bsdextrautils (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 110s Preparing to unpack .../eject_2.40.2-14ubuntu1_armhf.deb ... 110s Unpacking eject (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 110s Preparing to unpack .../fdisk_2.40.2-14ubuntu1_armhf.deb ... 110s Unpacking fdisk (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 110s Preparing to unpack .../libblkid1_2.40.2-14ubuntu1_armhf.deb ... 110s Unpacking libblkid1:armhf (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 110s Setting up libblkid1:armhf (2.40.2-14ubuntu1) ... 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 ... 59974 files and directories currently installed.) 110s Preparing to unpack .../libmount1_2.40.2-14ubuntu1_armhf.deb ... 110s Unpacking libmount1:armhf (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 110s Setting up libmount1:armhf (2.40.2-14ubuntu1) ... 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 ... 59974 files and directories currently installed.) 110s Preparing to unpack .../libsmartcols1_2.40.2-14ubuntu1_armhf.deb ... 110s Unpacking libsmartcols1:armhf (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 110s Setting up libsmartcols1:armhf (2.40.2-14ubuntu1) ... 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 .../libuuid1_2.40.2-14ubuntu1_armhf.deb ... 111s Unpacking libuuid1:armhf (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 111s Setting up libuuid1:armhf (2.40.2-14ubuntu1) ... 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 .../util-linux_2.40.2-14ubuntu1_armhf.deb ... 111s Unpacking util-linux (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 111s Setting up util-linux (2.40.2-14ubuntu1) ... 112s fstrim.service is a disabled or a static unit not running, not starting it. 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 ... 59967 files and directories currently installed.) 112s Preparing to unpack .../0-uuid-runtime_2.40.2-14ubuntu1_armhf.deb ... 112s Unpacking uuid-runtime (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 112s Preparing to unpack .../1-libfdisk1_2.40.2-14ubuntu1_armhf.deb ... 112s Unpacking libfdisk1:armhf (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 112s Preparing to unpack .../2-mount_2.40.2-14ubuntu1_armhf.deb ... 112s Unpacking mount (2.40.2-14ubuntu1) over (2.40.2-1ubuntu1) ... 112s Preparing to unpack .../3-readline-common_8.2-6_all.deb ... 112s Unpacking readline-common (8.2-6) over (8.2-5) ... 112s Preparing to unpack .../4-libreadline8t64_8.2-6_armhf.deb ... 112s Leaving 'diversion of /lib/arm-linux-gnueabihf/libhistory.so.8 to /lib/arm-linux-gnueabihf/libhistory.so.8.usr-is-merged by libreadline8t64' 112s 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' 112s Leaving 'diversion of /lib/arm-linux-gnueabihf/libreadline.so.8 to /lib/arm-linux-gnueabihf/libreadline.so.8.usr-is-merged by libreadline8t64' 112s 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' 112s Unpacking libreadline8t64:armhf (8.2-6) over (8.2-5) ... 112s Preparing to unpack .../5-systemd-cryptsetup_257.2-3ubuntu1_armhf.deb ... 112s Unpacking systemd-cryptsetup (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 112s Preparing to unpack .../6-libsystemd-shared_257.2-3ubuntu1_armhf.deb ... 112s Unpacking libsystemd-shared:armhf (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 112s Preparing to unpack .../7-libnss-systemd_257.2-3ubuntu1_armhf.deb ... 112s Unpacking libnss-systemd:armhf (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 112s Setting up libsystemd-shared:armhf (257.2-3ubuntu1) ... 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 ... 59967 files and directories currently installed.) 112s Preparing to unpack .../systemd_257.2-3ubuntu1_armhf.deb ... 112s Unpacking systemd (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 113s Preparing to unpack .../udev_257.2-3ubuntu1_armhf.deb ... 113s Unpacking udev (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 113s Preparing to unpack .../libudev1_257.2-3ubuntu1_armhf.deb ... 113s Unpacking libudev1:armhf (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 113s Setting up libudev1:armhf (257.2-3ubuntu1) ... 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 ... 59961 files and directories currently installed.) 113s Preparing to unpack .../libdevmapper1.02.1_2%3a1.02.201-1ubuntu1_armhf.deb ... 113s Unpacking libdevmapper1.02.1:armhf (2:1.02.201-1ubuntu1) over (2:1.02.196-1ubuntu2) ... 113s Preparing to unpack .../libcryptsetup12_2%3a2.7.5-1ubuntu2_armhf.deb ... 113s Unpacking libcryptsetup12:armhf (2:2.7.5-1ubuntu2) over (2:2.7.2-2ubuntu1) ... 113s Preparing to unpack .../libsystemd0_257.2-3ubuntu1_armhf.deb ... 113s Unpacking libsystemd0:armhf (257.2-3ubuntu1) over (256.5-2ubuntu4) ... 113s Setting up libsystemd0:armhf (257.2-3ubuntu1) ... 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 ... 59961 files and directories currently installed.) 113s Preparing to unpack .../libapt-pkg6.0t64_2.9.29_armhf.deb ... 113s Unpacking libapt-pkg6.0t64:armhf (2.9.29) over (2.9.14ubuntu1) ... 113s Setting up libapt-pkg6.0t64:armhf (2.9.29) ... 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 ... 59961 files and directories currently installed.) 113s Preparing to unpack .../tar_1.35+dfsg-3.1_armhf.deb ... 113s Unpacking tar (1.35+dfsg-3.1) over (1.35+dfsg-3build1) ... 113s Setting up tar (1.35+dfsg-3.1) ... 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 ... 59961 files and directories currently installed.) 114s Preparing to unpack .../dpkg_1.22.11ubuntu4_armhf.deb ... 114s Unpacking dpkg (1.22.11ubuntu4) over (1.22.11ubuntu3) ... 114s Setting up dpkg (1.22.11ubuntu4) ... 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 ... 59961 files and directories currently installed.) 114s Preparing to unpack .../gzip_1.13-1ubuntu2_armhf.deb ... 114s Unpacking gzip (1.13-1ubuntu2) over (1.12-1.1ubuntu1) ... 114s Setting up gzip (1.13-1ubuntu2) ... 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 ... 59961 files and directories currently installed.) 115s Preparing to unpack .../ncurses-bin_6.5+20250125-2_armhf.deb ... 115s Unpacking ncurses-bin (6.5+20250125-2) over (6.5-2) ... 115s Setting up ncurses-bin (6.5+20250125-2) ... 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 ... 59961 files and directories currently installed.) 115s Preparing to unpack .../perl_5.40.1-2_armhf.deb ... 115s Unpacking perl (5.40.1-2) over (5.40.0-8) ... 115s Preparing to unpack .../perl-modules-5.40_5.40.1-2_all.deb ... 115s Unpacking perl-modules-5.40 (5.40.1-2) over (5.40.0-8) ... 115s Preparing to unpack .../libperl5.40_5.40.1-2_armhf.deb ... 115s Unpacking libperl5.40:armhf (5.40.1-2) over (5.40.0-8) ... 115s Preparing to unpack .../perl-base_5.40.1-2_armhf.deb ... 115s Unpacking perl-base (5.40.1-2) over (5.40.0-8) ... 116s Setting up perl-base (5.40.1-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 ... 59961 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 ... 59961 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 ... 59961 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 ... 59961 files and directories currently installed.) 116s Preparing to unpack .../libc-bin_2.40-4ubuntu1_armhf.deb ... 116s Unpacking libc-bin (2.40-4ubuntu1) over (2.40-1ubuntu3) ... 116s Setting up libc-bin (2.40-4ubuntu1) ... 117s (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 ... 59961 files and directories currently installed.) 117s Preparing to unpack .../ncurses-base_6.5+20250125-2_all.deb ... 117s Unpacking ncurses-base (6.5+20250125-2) over (6.5-2) ... 117s Setting up ncurses-base (6.5+20250125-2) ... 117s (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 ... 59961 files and directories currently installed.) 117s Preparing to unpack .../0-ncurses-term_6.5+20250125-2_all.deb ... 117s Unpacking ncurses-term (6.5+20250125-2) over (6.5-2) ... 117s Preparing to unpack .../1-kbd_2.7.1-2ubuntu1_armhf.deb ... 117s Unpacking kbd (2.7.1-2ubuntu1) over (2.6.4-2ubuntu3) ... 117s Preparing to unpack .../2-console-setup-linux_1.226ubuntu3_all.deb ... 117s Unpacking console-setup-linux (1.226ubuntu3) over (1.226ubuntu2) ... 118s Preparing to unpack .../3-console-setup_1.226ubuntu3_all.deb ... 118s Unpacking console-setup (1.226ubuntu3) over (1.226ubuntu2) ... 118s Preparing to unpack .../4-keyboard-configuration_1.226ubuntu3_all.deb ... 118s Unpacking keyboard-configuration (1.226ubuntu3) over (1.226ubuntu2) ... 118s Preparing to unpack .../5-sysvinit-utils_3.14-1ubuntu1_armhf.deb ... 118s Unpacking sysvinit-utils (3.14-1ubuntu1) over (3.08-6ubuntu3) ... 118s Setting up sysvinit-utils (3.14-1ubuntu1) ... 118s Selecting previously unselected package libapt-pkg7.0:armhf. 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 .../libapt-pkg7.0_2.9.30ubuntu1_armhf.deb ... 118s Unpacking libapt-pkg7.0:armhf (2.9.30ubuntu1) ... 118s Setting up libapt-pkg7.0:armhf (2.9.30ubuntu1) ... 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 ... 60015 files and directories currently installed.) 118s Preparing to unpack .../apt_2.9.30ubuntu1_armhf.deb ... 118s Unpacking apt (2.9.30ubuntu1) over (2.9.14ubuntu1) ... 118s Setting up apt (2.9.30ubuntu1) ... 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 ... 60017 files and directories currently installed.) 119s Preparing to unpack .../apt-utils_2.9.30ubuntu1_armhf.deb ... 119s Unpacking apt-utils (2.9.30ubuntu1) over (2.9.14ubuntu1) ... 119s Preparing to unpack .../libgpg-error-l10n_1.51-3_all.deb ... 119s Unpacking libgpg-error-l10n (1.51-3) over (1.50-4) ... 119s Preparing to unpack .../libgpg-error0_1.51-3_armhf.deb ... 119s Unpacking libgpg-error0:armhf (1.51-3) over (1.50-4) ... 119s Setting up libgpg-error0:armhf (1.51-3) ... 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 ... 60017 files and directories currently installed.) 119s Preparing to unpack .../libnpth0t64_1.8-2_armhf.deb ... 119s Unpacking libnpth0t64:armhf (1.8-2) over (1.6-3.1build1) ... 119s Setting up libnpth0t64:armhf (1.8-2) ... 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 ... 60017 files and directories currently installed.) 119s Preparing to unpack .../00-gpg-wks-client_2.4.4-2ubuntu22_armhf.deb ... 119s Unpacking gpg-wks-client (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 119s Preparing to unpack .../01-dirmngr_2.4.4-2ubuntu22_armhf.deb ... 119s Unpacking dirmngr (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 119s Preparing to unpack .../02-gpgsm_2.4.4-2ubuntu22_armhf.deb ... 119s Unpacking gpgsm (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 119s Preparing to unpack .../03-gnupg-utils_2.4.4-2ubuntu22_armhf.deb ... 119s Unpacking gnupg-utils (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 119s Preparing to unpack .../04-gpg-agent_2.4.4-2ubuntu22_armhf.deb ... 119s Unpacking gpg-agent (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 119s Preparing to unpack .../05-gpg_2.4.4-2ubuntu22_armhf.deb ... 119s Unpacking gpg (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 119s Preparing to unpack .../06-gpgconf_2.4.4-2ubuntu22_armhf.deb ... 119s Unpacking gpgconf (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 119s Preparing to unpack .../07-gnupg_2.4.4-2ubuntu22_all.deb ... 119s Unpacking gnupg (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 120s Preparing to unpack .../08-keyboxd_2.4.4-2ubuntu22_armhf.deb ... 120s Unpacking keyboxd (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 120s Preparing to unpack .../09-pinentry-curses_1.3.1-2ubuntu2_armhf.deb ... 120s Unpacking pinentry-curses (1.3.1-2ubuntu2) over (1.3.1-0ubuntu2) ... 120s Preparing to unpack .../10-libnettle8t64_3.10.1-1_armhf.deb ... 120s Unpacking libnettle8t64:armhf (3.10.1-1) over (3.10-1) ... 120s Setting up libnettle8t64:armhf (3.10.1-1) ... 120s (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 ... 60017 files and directories currently installed.) 120s Preparing to unpack .../libhogweed6t64_3.10.1-1_armhf.deb ... 120s Unpacking libhogweed6t64:armhf (3.10.1-1) over (3.10-1) ... 120s Setting up libhogweed6t64:armhf (3.10.1-1) ... 120s (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 ... 60017 files and directories currently installed.) 120s Preparing to unpack .../libffi8_3.4.7-1_armhf.deb ... 120s Unpacking libffi8:armhf (3.4.7-1) over (3.4.6-1build1) ... 120s Setting up libffi8:armhf (3.4.7-1) ... 120s (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 ... 60017 files and directories currently installed.) 120s Preparing to unpack .../libp11-kit0_0.25.5-2ubuntu3_armhf.deb ... 120s Unpacking libp11-kit0:armhf (0.25.5-2ubuntu3) over (0.25.5-2ubuntu1) ... 120s Setting up libp11-kit0:armhf (0.25.5-2ubuntu3) ... 120s (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 ... 60017 files and directories currently installed.) 120s Preparing to unpack .../libtasn1-6_4.20.0-2_armhf.deb ... 120s Unpacking libtasn1-6:armhf (4.20.0-2) over (4.19.0-3build1) ... 120s Setting up libtasn1-6:armhf (4.20.0-2) ... 120s (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 ... 60017 files and directories currently installed.) 120s Preparing to unpack .../libunistring5_1.3-1_armhf.deb ... 120s Unpacking libunistring5:armhf (1.3-1) over (1.2-1) ... 120s Setting up libunistring5:armhf (1.3-1) ... 120s (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 ... 60017 files and directories currently installed.) 120s Preparing to unpack .../libgnutls30t64_3.8.9-2ubuntu2_armhf.deb ... 120s Unpacking libgnutls30t64:armhf (3.8.9-2ubuntu2) over (3.8.8-2ubuntu1) ... 120s Setting up libgnutls30t64:armhf (3.8.9-2ubuntu2) ... 120s (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 ... 60017 files and directories currently installed.) 120s Preparing to unpack .../libsasl2-modules-db_2.1.28+dfsg1-8build1_armhf.deb ... 120s Unpacking libsasl2-modules-db:armhf (2.1.28+dfsg1-8build1) over (2.1.28+dfsg1-8) ... 120s Preparing to unpack .../libsasl2-2_2.1.28+dfsg1-8build1_armhf.deb ... 120s Unpacking libsasl2-2:armhf (2.1.28+dfsg1-8build1) over (2.1.28+dfsg1-8) ... 120s Preparing to unpack .../libldap-common_2.6.9+dfsg-1~exp2ubuntu1_all.deb ... 120s Unpacking libldap-common (2.6.9+dfsg-1~exp2ubuntu1) over (2.6.8+dfsg-1~exp4ubuntu3) ... 120s Preparing to unpack .../libldap2_2.6.9+dfsg-1~exp2ubuntu1_armhf.deb ... 120s Unpacking libldap2:armhf (2.6.9+dfsg-1~exp2ubuntu1) over (2.6.8+dfsg-1~exp4ubuntu3) ... 121s Preparing to unpack .../gpgv_2.4.4-2ubuntu22_armhf.deb ... 121s Unpacking gpgv (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 121s Setting up gpgv (2.4.4-2ubuntu22) ... 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 ... 60016 files and directories currently installed.) 121s Preparing to unpack .../0-e2fsprogs-l10n_1.47.2-1ubuntu1_all.deb ... 121s Unpacking e2fsprogs-l10n (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 121s Preparing to unpack .../1-logsave_1.47.2-1ubuntu1_armhf.deb ... 121s Unpacking logsave (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 121s Preparing to unpack .../2-ubuntu-minimal_1.547_armhf.deb ... 121s Unpacking ubuntu-minimal (1.547) over (1.544) ... 121s Preparing to unpack .../3-initramfs-tools_0.145ubuntu2_all.deb ... 121s Unpacking initramfs-tools (0.145ubuntu2) over (0.142ubuntu35) ... 121s Preparing to unpack .../4-initramfs-tools-core_0.145ubuntu2_all.deb ... 121s Unpacking initramfs-tools-core (0.145ubuntu2) over (0.142ubuntu35) ... 121s Preparing to unpack .../5-libext2fs2t64_1.47.2-1ubuntu1_armhf.deb ... 121s Leaving 'diversion of /lib/arm-linux-gnueabihf/libe2p.so.2 to /lib/arm-linux-gnueabihf/libe2p.so.2.usr-is-merged by libext2fs2t64' 121s 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' 121s Leaving 'diversion of /lib/arm-linux-gnueabihf/libext2fs.so.2 to /lib/arm-linux-gnueabihf/libext2fs.so.2.usr-is-merged by libext2fs2t64' 121s 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' 121s Unpacking libext2fs2t64:armhf (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 121s Setting up libext2fs2t64:armhf (1.47.2-1ubuntu1) ... 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 ... 60016 files and directories currently installed.) 121s Preparing to unpack .../e2fsprogs_1.47.2-1ubuntu1_armhf.deb ... 121s Unpacking e2fsprogs (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 121s Preparing to unpack .../dhcpcd-base_1%3a10.1.0-7_armhf.deb ... 121s Unpacking dhcpcd-base (1:10.1.0-7) over (1:10.1.0-2) ... 121s Setting up libapparmor1:armhf (4.1.0~beta5-0ubuntu5) ... 121s Setting up mount (2.40.2-14ubuntu1) ... 121s Setting up systemd (257.2-3ubuntu1) ... 121s Installing new version of config file /etc/systemd/logind.conf ... 121s Installing new version of config file /etc/systemd/sleep.conf ... 121s /usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", ignoring. 121s Created symlink '/run/systemd/system/tmp.mount' → '/dev/null'. 121s /usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", ignoring. 122s Setting up systemd-sysv (257.2-3ubuntu1) ... 122s (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 ... 60015 files and directories currently installed.) 122s Preparing to unpack .../00-init_1.68_armhf.deb ... 122s Unpacking init (1.68) over (1.67ubuntu1) ... 122s Preparing to unpack .../01-libbpf1_1%3a1.5.0-2_armhf.deb ... 122s Unpacking libbpf1:armhf (1:1.5.0-2) over (1:1.5.0-1) ... 122s Preparing to unpack .../02-iptables_1.8.11-2ubuntu1_armhf.deb ... 122s Unpacking iptables (1.8.11-2ubuntu1) over (1.8.10-3ubuntu2) ... 122s Preparing to unpack .../03-libip4tc2_1.8.11-2ubuntu1_armhf.deb ... 122s Unpacking libip4tc2:armhf (1.8.11-2ubuntu1) over (1.8.10-3ubuntu2) ... 122s Preparing to unpack .../04-libip6tc2_1.8.11-2ubuntu1_armhf.deb ... 122s Unpacking libip6tc2:armhf (1.8.11-2ubuntu1) over (1.8.10-3ubuntu2) ... 122s Preparing to unpack .../05-libnftnl11_1.2.8-1_armhf.deb ... 122s Unpacking libnftnl11:armhf (1.2.8-1) over (1.2.7-1) ... 122s Preparing to unpack .../06-libxtables12_1.8.11-2ubuntu1_armhf.deb ... 122s Unpacking libxtables12:armhf (1.8.11-2ubuntu1) over (1.8.10-3ubuntu2) ... 122s Preparing to unpack .../07-iproute2_6.13.0-1ubuntu1_armhf.deb ... 123s Unpacking iproute2 (6.13.0-1ubuntu1) over (6.10.0-2ubuntu1) ... 123s Preparing to unpack .../08-iputils-ping_3%3a20240905-1ubuntu1_armhf.deb ... 123s Unpacking iputils-ping (3:20240905-1ubuntu1) over (3:20240117-1build1) ... 123s Preparing to unpack .../09-locales_2.40-4ubuntu1_all.deb ... 123s Unpacking locales (2.40-4ubuntu1) over (2.40-1ubuntu3) ... 123s Selecting previously unselected package login.defs. 123s Preparing to unpack .../10-login.defs_1%3a4.16.0-7ubuntu1_all.deb ... 123s Unpacking login.defs (1:4.16.0-7ubuntu1) ... 123s Replacing files in old package login (1:4.15.3-3ubuntu2) ... 123s Setting up login.defs (1:4.16.0-7ubuntu1) ... 123s Installing new version of config file /etc/login.defs ... 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 ... 60022 files and directories currently installed.) 123s Preparing to unpack .../0-login_1%3a4.16.0-2+really2.40.2-14ubuntu1_armhf.deb ... 123s Unpacking login (1:4.16.0-2+really2.40.2-14ubuntu1) over (1:4.15.3-3ubuntu2) ... 123s Preparing to unpack .../1-mawk_1.3.4.20250131-1_armhf.deb ... 123s Unpacking mawk (1.3.4.20250131-1) over (1.3.4.20240905-1) ... 123s Preparing to unpack .../2-netcat-openbsd_1.228-1_armhf.deb ... 123s Unpacking netcat-openbsd (1.228-1) over (1.226-1.1) ... 123s Selecting previously unselected package libpython3.13-minimal:armhf. 123s Preparing to unpack .../3-libpython3.13-minimal_3.13.2-1_armhf.deb ... 123s Unpacking libpython3.13-minimal:armhf (3.13.2-1) ... 123s Selecting previously unselected package python3.13-minimal. 124s Preparing to unpack .../4-python3.13-minimal_3.13.2-1_armhf.deb ... 124s Unpacking python3.13-minimal (3.13.2-1) ... 124s Preparing to unpack .../5-python3-cryptography_43.0.0-1_armhf.deb ... 124s Unpacking python3-cryptography (43.0.0-1) over (42.0.5-2build1) ... 124s Setting up libpython3.13-minimal:armhf (3.13.2-1) ... 124s Setting up python3.13-minimal (3.13.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 ... 60304 files and directories currently installed.) 125s Preparing to unpack .../python3-minimal_3.13.1-1~exp2_armhf.deb ... 125s Unpacking python3-minimal (3.13.1-1~exp2) over (3.12.6-0ubuntu1) ... 125s Setting up python3-minimal (3.13.1-1~exp2) ... 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 ... 60304 files and directories currently installed.) 125s Preparing to unpack .../00-python3_3.13.1-1~exp2_armhf.deb ... 125s Unpacking python3 (3.13.1-1~exp2) over (3.12.6-0ubuntu1) ... 125s Selecting previously unselected package python3-bcrypt. 125s Preparing to unpack .../01-python3-bcrypt_4.2.0-2.1_armhf.deb ... 125s Unpacking python3-bcrypt (4.2.0-2.1) ... 125s Preparing to unpack .../02-tzdata_2025a-2ubuntu1_all.deb ... 125s Unpacking tzdata (2025a-2ubuntu1) over (2024b-1ubuntu2) ... 125s Selecting previously unselected package libpython3.13-stdlib:armhf. 125s Preparing to unpack .../03-libpython3.13-stdlib_3.13.2-1_armhf.deb ... 125s Unpacking libpython3.13-stdlib:armhf (3.13.2-1) ... 126s Selecting previously unselected package python3.13. 126s Preparing to unpack .../04-python3.13_3.13.2-1_armhf.deb ... 126s Unpacking python3.13 (3.13.2-1) ... 126s Preparing to unpack .../05-libpython3-stdlib_3.13.1-1~exp2_armhf.deb ... 126s Unpacking libpython3-stdlib:armhf (3.13.1-1~exp2) over (3.12.6-0ubuntu1) ... 126s Preparing to unpack .../06-gir1.2-girepository-2.0_1.82.0-4_armhf.deb ... 126s Unpacking gir1.2-girepository-2.0:armhf (1.82.0-4) over (1.82.0-2) ... 126s Preparing to unpack .../07-gir1.2-glib-2.0_2.83.4-1_armhf.deb ... 126s Unpacking gir1.2-glib-2.0:armhf (2.83.4-1) over (2.82.2-3) ... 126s Preparing to unpack .../08-libgirepository-1.0-1_1.82.0-4_armhf.deb ... 126s Unpacking libgirepository-1.0-1:armhf (1.82.0-4) over (1.82.0-2) ... 126s Preparing to unpack .../09-libglib2.0-data_2.83.4-1_all.deb ... 126s Unpacking libglib2.0-data (2.83.4-1) over (2.82.2-3) ... 126s Preparing to unpack .../10-libglib2.0-bin_2.83.4-1_armhf.deb ... 126s Unpacking libglib2.0-bin (2.83.4-1) over (2.82.2-3) ... 126s Preparing to unpack .../11-libatomic1_15-20250213-1ubuntu1_armhf.deb ... 126s Unpacking libatomic1:armhf (15-20250213-1ubuntu1) over (14.2.0-8ubuntu1) ... 126s Preparing to unpack .../12-libglib2.0-0t64_2.83.4-1_armhf.deb ... 126s Unpacking libglib2.0-0t64:armhf (2.83.4-1) over (2.82.2-3) ... 126s Preparing to unpack .../13-netplan-generator_1.1.2-2ubuntu1_armhf.deb ... 126s Adding 'diversion of /lib/systemd/system-generators/netplan to /lib/systemd/system-generators/netplan.usr-is-merged by netplan-generator' 126s Unpacking netplan-generator (1.1.2-2ubuntu1) over (1.1.1-1) ... 126s Preparing to unpack .../14-libyaml-0-2_0.2.5-2_armhf.deb ... 126s Unpacking libyaml-0-2:armhf (0.2.5-2) over (0.2.5-1build1) ... 126s Preparing to unpack .../15-python3-netplan_1.1.2-2ubuntu1_armhf.deb ... 126s /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. 126s for fn in glob1(directory, "%s.*" % fname): 126s Unpacking python3-netplan (1.1.2-2ubuntu1) over (1.1.1-1) ... 126s Preparing to unpack .../16-netplan.io_1.1.2-2ubuntu1_armhf.deb ... 126s Unpacking netplan.io (1.1.2-2ubuntu1) over (1.1.1-1) ... 126s Preparing to unpack .../17-libnetplan1_1.1.2-2ubuntu1_armhf.deb ... 126s Unpacking libnetplan1:armhf (1.1.2-2ubuntu1) over (1.1.1-1) ... 126s Preparing to unpack .../18-ethtool_1%3a6.11-1_armhf.deb ... 126s Unpacking ethtool (1:6.11-1) over (1:6.10-1) ... 126s Preparing to unpack .../19-libsemanage-common_3.7-2.1_all.deb ... 126s Unpacking libsemanage-common (3.7-2.1) over (3.7-2build1) ... 126s Setting up libsemanage-common (3.7-2.1) ... 126s (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 ... 60727 files and directories currently installed.) 126s Preparing to unpack .../libsemanage2_3.7-2.1_armhf.deb ... 126s Unpacking libsemanage2:armhf (3.7-2.1) over (3.7-2build1) ... 126s Setting up libsemanage2:armhf (3.7-2.1) ... 126s (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 ... 60727 files and directories currently installed.) 126s Preparing to unpack .../passwd_1%3a4.16.0-7ubuntu1_armhf.deb ... 127s Unpacking passwd (1:4.16.0-7ubuntu1) over (1:4.15.3-3ubuntu2) ... 127s Setting up passwd (1:4.16.0-7ubuntu1) ... 127s (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 ... 60762 files and directories currently installed.) 127s Preparing to unpack .../000-ubuntu-pro-client-l10n_34.1.3_armhf.deb ... 127s Unpacking ubuntu-pro-client-l10n (34.1.3) over (34.1.2) ... 127s Preparing to unpack .../001-python-apt-common_2.9.9_all.deb ... 127s Unpacking python-apt-common (2.9.9) over (2.9.0ubuntu2) ... 127s Preparing to unpack .../002-python3-apt_2.9.9_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.9) over (2.9.0ubuntu2) ... 127s Preparing to unpack .../003-distro-info_1.13_armhf.deb ... 127s Unpacking distro-info (1.13) over (1.12) ... 127s Preparing to unpack .../004-ubuntu-pro-client_34.1.3_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 ubuntu-pro-client (34.1.3) over (34.1.2) ... 127s Preparing to unpack .../005-vim-tiny_2%3a9.1.0967-1ubuntu2_armhf.deb ... 127s Unpacking vim-tiny (2:9.1.0967-1ubuntu2) over (2:9.1.0861-1ubuntu1) ... 127s Preparing to unpack .../006-vim-common_2%3a9.1.0967-1ubuntu2_all.deb ... 127s Unpacking vim-common (2:9.1.0967-1ubuntu2) over (2:9.1.0861-1ubuntu1) ... 127s Preparing to unpack .../007-python3-newt_0.52.24-4ubuntu1_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-newt:armhf (0.52.24-4ubuntu1) over (0.52.24-2ubuntu4) ... 127s Preparing to unpack .../008-libnewt0.52_0.52.24-4ubuntu1_armhf.deb ... 127s Unpacking libnewt0.52:armhf (0.52.24-4ubuntu1) over (0.52.24-2ubuntu4) ... 128s Preparing to unpack .../009-whiptail_0.52.24-4ubuntu1_armhf.deb ... 128s Unpacking whiptail (0.52.24-4ubuntu1) over (0.52.24-2ubuntu4) ... 128s Preparing to unpack .../010-dracut-install_106-2ubuntu1_armhf.deb ... 128s Unpacking dracut-install (106-2ubuntu1) over (105-2ubuntu3) ... 128s Preparing to unpack .../011-initramfs-tools-bin_0.145ubuntu2_armhf.deb ... 128s Unpacking initramfs-tools-bin (0.145ubuntu2) over (0.142ubuntu35) ... 128s Preparing to unpack .../012-busybox-initramfs_1%3a1.37.0-4ubuntu1_armhf.deb ... 128s Unpacking busybox-initramfs (1:1.37.0-4ubuntu1) over (1:1.36.1-9ubuntu1) ... 128s Preparing to unpack .../013-python3.12_3.12.9-1_armhf.deb ... 128s Unpacking python3.12 (3.12.9-1) over (3.12.7-3) ... 128s Preparing to unpack .../014-libpython3.12-stdlib_3.12.9-1_armhf.deb ... 128s Unpacking libpython3.12-stdlib:armhf (3.12.9-1) over (3.12.7-3) ... 128s Preparing to unpack .../015-python3.12-minimal_3.12.9-1_armhf.deb ... 128s Unpacking python3.12-minimal (3.12.9-1) over (3.12.7-3) ... 128s Preparing to unpack .../016-libpython3.12-minimal_3.12.9-1_armhf.deb ... 128s Unpacking libpython3.12-minimal:armhf (3.12.9-1) over (3.12.7-3) ... 128s Preparing to unpack .../017-cron_3.0pl1-192ubuntu1_armhf.deb ... 128s Unpacking cron (3.0pl1-192ubuntu1) over (3.0pl1-189ubuntu1) ... 128s Preparing to unpack .../018-rsync_3.4.1-0syncable1_armhf.deb ... 128s Unpacking rsync (3.4.1-0syncable1) over (3.3.0-1) ... 128s Preparing to unpack .../019-python3-lazr.uri_1.0.6-5_all.deb ... 128s /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. 128s for fn in glob1(directory, "%s.*" % fname): 128s Unpacking python3-lazr.uri (1.0.6-5) over (1.0.6-4) ... 128s Preparing to unpack .../020-python3-launchpadlib_2.1.0-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-launchpadlib (2.1.0-1) over (2.0.0-1) ... 129s Preparing to unpack .../021-python3-problem-report_2.31.0+git20250220-0ubuntu1_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-problem-report (2.31.0+git20250220-0ubuntu1) over (2.30.0-0ubuntu5) ... 129s Preparing to unpack .../022-python3-apport_2.31.0+git20250220-0ubuntu1_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-apport (2.31.0+git20250220-0ubuntu1) over (2.30.0-0ubuntu5) ... 129s Preparing to unpack .../023-python3-gi_3.50.0-4_armhf.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-gi (3.50.0-4) over (3.50.0-3build1) ... 129s Preparing to unpack .../024-apport-core-dump-handler_2.31.0+git20250220-0ubuntu1_all.deb ... 129s Unpacking apport-core-dump-handler (2.31.0+git20250220-0ubuntu1) over (2.30.0-0ubuntu5) ... 129s Preparing to unpack .../025-apport_2.31.0+git20250220-0ubuntu1_all.deb ... 129s Unpacking apport (2.31.0+git20250220-0ubuntu1) over (2.30.0-0ubuntu5) ... 129s Preparing to unpack .../026-gcc-14-base_14.2.0-17ubuntu3_armhf.deb ... 129s Unpacking gcc-14-base:armhf (14.2.0-17ubuntu3) over (14.2.0-8ubuntu1) ... 129s Preparing to unpack .../027-libcom-err2_1.47.2-1ubuntu1_armhf.deb ... 129s Unpacking libcom-err2:armhf (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 129s Preparing to unpack .../028-libss2_1.47.2-1ubuntu1_armhf.deb ... 129s Unpacking libss2:armhf (1.47.2-1ubuntu1) over (1.47.1-1ubuntu1) ... 129s Preparing to unpack .../029-openssl_3.4.1-1ubuntu1_armhf.deb ... 129s Unpacking openssl (3.4.1-1ubuntu1) over (3.3.1-2ubuntu2) ... 129s Preparing to unpack .../030-ca-certificates_20241223_all.deb ... 129s Unpacking ca-certificates (20241223) over (20240203) ... 130s Preparing to unpack .../031-krb5-locales_1.21.3-4ubuntu1_all.deb ... 130s Unpacking krb5-locales (1.21.3-4ubuntu1) over (1.21.3-3) ... 130s Preparing to unpack .../032-libfribidi0_1.0.16-1_armhf.deb ... 130s Unpacking libfribidi0:armhf (1.0.16-1) over (1.0.15-1) ... 130s Preparing to unpack .../033-libgssapi-krb5-2_1.21.3-4ubuntu1_armhf.deb ... 130s Unpacking libgssapi-krb5-2:armhf (1.21.3-4ubuntu1) over (1.21.3-3) ... 130s Preparing to unpack .../034-libkrb5-3_1.21.3-4ubuntu1_armhf.deb ... 130s Unpacking libkrb5-3:armhf (1.21.3-4ubuntu1) over (1.21.3-3) ... 130s Preparing to unpack .../035-libkrb5support0_1.21.3-4ubuntu1_armhf.deb ... 130s Unpacking libkrb5support0:armhf (1.21.3-4ubuntu1) over (1.21.3-3) ... 130s Preparing to unpack .../036-libk5crypto3_1.21.3-4ubuntu1_armhf.deb ... 130s Unpacking libk5crypto3:armhf (1.21.3-4ubuntu1) over (1.21.3-3) ... 130s Preparing to unpack .../037-libicu74_74.2-1ubuntu6_armhf.deb ... 130s Unpacking libicu74:armhf (74.2-1ubuntu6) over (74.2-1ubuntu4) ... 130s Preparing to unpack .../038-libxml2_2.12.7+dfsg+really2.9.14-0.2ubuntu3_armhf.deb ... 130s Unpacking libxml2:armhf (2.12.7+dfsg+really2.9.14-0.2ubuntu3) over (2.12.7+dfsg-3) ... 130s Preparing to unpack .../039-python3-pygments_2.18.0+dfsg-2_all.deb ... 130s /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. 130s for fn in glob1(directory, "%s.*" % fname): 130s Unpacking python3-pygments (2.18.0+dfsg-2) over (2.18.0+dfsg-1ubuntu1) ... 131s Preparing to unpack .../040-python3-rich_13.9.4-1_all.deb ... 131s /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. 131s for fn in glob1(directory, "%s.*" % fname): 131s Unpacking python3-rich (13.9.4-1) over (13.7.1-1) ... 131s Preparing to unpack .../041-ucf_3.0050_all.deb ... 131s Unpacking ucf (3.0050) over (3.0043+nmu1) ... 131s Preparing to unpack .../042-rsyslog_8.2412.0-2ubuntu1_armhf.deb ... 131s Unpacking rsyslog (8.2412.0-2ubuntu1) over (8.2406.0-1ubuntu2) ... 131s Preparing to unpack .../043-xxd_2%3a9.1.0967-1ubuntu2_armhf.deb ... 131s Unpacking xxd (2:9.1.0967-1ubuntu2) over (2:9.1.0861-1ubuntu1) ... 131s Preparing to unpack .../044-apparmor_4.1.0~beta5-0ubuntu5_armhf.deb ... 132s Unpacking apparmor (4.1.0~beta5-0ubuntu5) over (4.1.0~beta1-0ubuntu4) ... 132s dpkg: warning: unable to delete old directory '/lib/apparmor': Directory not empty 132s Preparing to unpack .../045-bash-completion_1%3a2.16.0-7_all.deb ... 132s Unpacking bash-completion (1:2.16.0-7) over (1:2.14.0-2) ... 133s Selecting previously unselected package libjemalloc2:armhf. 133s Preparing to unpack .../046-libjemalloc2_5.3.0-2build1_armhf.deb ... 133s Unpacking libjemalloc2:armhf (5.3.0-2build1) ... 133s Preparing to unpack .../047-libmaxminddb0_1.12.2-1_armhf.deb ... 133s Unpacking libmaxminddb0:armhf (1.12.2-1) over (1.11.0-1) ... 133s Preparing to unpack .../048-liburcu8t64_0.15.1-1_armhf.deb ... 133s Unpacking liburcu8t64:armhf (0.15.1-1) over (0.14.1-1) ... 133s Preparing to unpack .../049-bind9-dnsutils_1%3a9.20.4-3ubuntu1_armhf.deb ... 133s Unpacking bind9-dnsutils (1:9.20.4-3ubuntu1) over (1:9.20.0-2ubuntu3) ... 133s Preparing to unpack .../050-bind9-host_1%3a9.20.4-3ubuntu1_armhf.deb ... 133s Unpacking bind9-host (1:9.20.4-3ubuntu1) over (1:9.20.0-2ubuntu3) ... 133s Preparing to unpack .../051-bind9-libs_1%3a9.20.4-3ubuntu1_armhf.deb ... 133s Unpacking bind9-libs:armhf (1:9.20.4-3ubuntu1) over (1:9.20.0-2ubuntu3) ... 133s Preparing to unpack .../052-libedit2_3.1-20250104-1_armhf.deb ... 133s Unpacking libedit2:armhf (3.1-20250104-1) over (3.1-20240808-1) ... 133s Preparing to unpack .../053-busybox-static_1%3a1.37.0-4ubuntu1_armhf.deb ... 133s Unpacking busybox-static (1:1.37.0-4ubuntu1) over (1:1.36.1-9ubuntu1) ... 133s Preparing to unpack .../054-cron-daemon-common_3.0pl1-192ubuntu1_all.deb ... 133s Unpacking cron-daemon-common (3.0pl1-192ubuntu1) over (3.0pl1-189ubuntu1) ... 133s Preparing to unpack .../055-dmsetup_2%3a1.02.201-1ubuntu1_armhf.deb ... 133s Unpacking dmsetup (2:1.02.201-1ubuntu1) over (2:1.02.196-1ubuntu2) ... 133s Preparing to unpack .../056-ed_1.21-1_armhf.deb ... 133s Unpacking ed (1.21-1) over (1.20.2-2) ... 133s Preparing to unpack .../057-gettext-base_0.23.1-1_armhf.deb ... 133s Unpacking gettext-base (0.23.1-1) over (0.22.5-2) ... 133s Preparing to unpack .../058-groff-base_1.23.0-7_armhf.deb ... 133s Unpacking groff-base (1.23.0-7) over (1.23.0-5) ... 133s Preparing to unpack .../059-libibverbs1_55.0-1ubuntu1_armhf.deb ... 133s Unpacking libibverbs1:armhf (55.0-1ubuntu1) over (52.0-2ubuntu1) ... 133s Preparing to unpack .../060-ibverbs-providers_55.0-1ubuntu1_armhf.deb ... 133s Unpacking ibverbs-providers:armhf (55.0-1ubuntu1) over (52.0-2ubuntu1) ... 133s Preparing to unpack .../061-inetutils-telnet_2%3a2.5-6ubuntu1_armhf.deb ... 133s Unpacking inetutils-telnet (2:2.5-6ubuntu1) over (2:2.5-5ubuntu1) ... 133s Preparing to unpack .../062-iputils-tracepath_3%3a20240905-1ubuntu1_armhf.deb ... 133s Unpacking iputils-tracepath (3:20240905-1ubuntu1) over (3:20240117-1build1) ... 134s Preparing to unpack .../063-libcbor0.10_0.10.2-2ubuntu1_armhf.deb ... 134s Unpacking libcbor0.10:armhf (0.10.2-2ubuntu1) over (0.10.2-1.2ubuntu2) ... 134s Preparing to unpack .../064-nftables_1.1.1-1build1_armhf.deb ... 134s Unpacking nftables (1.1.1-1build1) over (1.1.0-2) ... 134s Preparing to unpack .../065-libnftables1_1.1.1-1build1_armhf.deb ... 134s Unpacking libnftables1:armhf (1.1.1-1build1) over (1.1.0-2) ... 134s Preparing to unpack .../066-libpcap0.8t64_1.10.5-2ubuntu1_armhf.deb ... 134s Unpacking libpcap0.8t64:armhf (1.10.5-2ubuntu1) over (1.10.5-1ubuntu1) ... 134s Preparing to unpack .../067-libpng16-16t64_1.6.46-4_armhf.deb ... 134s Unpacking libpng16-16t64:armhf (1.6.46-4) over (1.6.44-2) ... 134s Preparing to unpack .../068-libxkbcommon0_1.7.0-2_armhf.deb ... 134s Unpacking libxkbcommon0:armhf (1.7.0-2) over (1.7.0-1) ... 134s Preparing to unpack .../069-libplymouth5_24.004.60-2ubuntu5_armhf.deb ... 134s Unpacking libplymouth5:armhf (24.004.60-2ubuntu5) over (24.004.60-2ubuntu4) ... 134s Preparing to unpack .../070-libtraceevent1-plugin_1%3a1.8.4-2_armhf.deb ... 134s Unpacking libtraceevent1-plugin:armhf (1:1.8.4-2) over (1:1.8.4-1) ... 134s Preparing to unpack .../071-libtraceevent1_1%3a1.8.4-2_armhf.deb ... 134s Unpacking libtraceevent1:armhf (1:1.8.4-2) over (1:1.8.4-1) ... 134s Preparing to unpack .../072-libusb-1.0-0_2%3a1.0.27-2_armhf.deb ... 134s Unpacking libusb-1.0-0:armhf (2:1.0.27-2) over (2:1.0.27-1) ... 134s Preparing to unpack .../073-libxdmcp6_1%3a1.1.5-1_armhf.deb ... 134s Unpacking libxdmcp6:armhf (1:1.1.5-1) over (1:1.1.3-0ubuntu6) ... 134s Preparing to unpack .../074-lshw_02.19.git.2021.06.19.996aaad9c7-2.1ubuntu1_armhf.deb ... 134s Unpacking lshw (02.19.git.2021.06.19.996aaad9c7-2.1ubuntu1) over (02.19.git.2021.06.19.996aaad9c7-2ubuntu2) ... 134s Preparing to unpack .../075-lsof_4.99.4+dfsg-2_armhf.deb ... 134s Unpacking lsof (4.99.4+dfsg-2) over (4.99.3+dfsg-2) ... 134s Preparing to unpack .../076-liblsof0_4.99.4+dfsg-2_armhf.deb ... 134s Unpacking liblsof0 (4.99.4+dfsg-2) over (4.99.3+dfsg-2) ... 134s Preparing to unpack .../077-nano_8.3-1_armhf.deb ... 134s Unpacking nano (8.3-1) over (8.2-1) ... 134s Preparing to unpack .../078-pci.ids_0.0~2025.02.12-1_all.deb ... 134s Unpacking pci.ids (0.0~2025.02.12-1) over (0.0~2024.10.24-1) ... 134s Preparing to unpack .../079-plymouth-theme-ubuntu-text_24.004.60-2ubuntu5_armhf.deb ... 134s Unpacking plymouth-theme-ubuntu-text (24.004.60-2ubuntu5) over (24.004.60-2ubuntu4) ... 134s Preparing to unpack .../080-libpackagekit-glib2-18_1.3.0-3build1_armhf.deb ... 134s Unpacking libpackagekit-glib2-18:armhf (1.3.0-3build1) over (1.3.0-2) ... 134s Preparing to unpack .../081-packagekit-tools_1.3.0-3build1_armhf.deb ... 134s Unpacking packagekit-tools (1.3.0-3build1) over (1.3.0-2) ... 134s Preparing to unpack .../082-polkitd_126-2_armhf.deb ... 135s Unpacking polkitd (126-2) over (125-2ubuntu1) ... 135s Preparing to unpack .../083-libpolkit-agent-1-0_126-2_armhf.deb ... 135s Unpacking libpolkit-agent-1-0:armhf (126-2) over (125-2ubuntu1) ... 135s Preparing to unpack .../084-libpolkit-gobject-1-0_126-2_armhf.deb ... 135s Unpacking libpolkit-gobject-1-0:armhf (126-2) over (125-2ubuntu1) ... 135s Preparing to unpack .../085-libcurl3t64-gnutls_8.12.0+git20250209.89ed161+ds-1ubuntu1_armhf.deb ... 135s Unpacking libcurl3t64-gnutls:armhf (8.12.0+git20250209.89ed161+ds-1ubuntu1) over (8.11.0-1ubuntu2) ... 135s Preparing to unpack .../086-libappstream5_1.0.4-1_armhf.deb ... 135s Unpacking libappstream5:armhf (1.0.4-1) over (1.0.3-1) ... 135s Preparing to unpack .../087-libgstreamer1.0-0_1.25.50-1_armhf.deb ... 135s Unpacking libgstreamer1.0-0:armhf (1.25.50-1) over (1.24.9-1) ... 135s Preparing to unpack .../088-packagekit_1.3.0-3build1_armhf.deb ... 135s Unpacking packagekit (1.3.0-3build1) over (1.3.0-2) ... 135s Preparing to unpack .../089-plymouth_24.004.60-2ubuntu5_armhf.deb ... 135s Unpacking plymouth (24.004.60-2ubuntu5) over (24.004.60-2ubuntu4) ... 135s Preparing to unpack .../090-powermgmt-base_1.38_all.deb ... 135s Unpacking powermgmt-base (1.38) over (1.37+nmu1ubuntu1) ... 135s Preparing to unpack .../091-psmisc_23.7-2_armhf.deb ... 135s Unpacking psmisc (23.7-2) over (23.7-1build1) ... 135s Preparing to unpack .../092-publicsuffix_20250108.1153-0.1_all.deb ... 135s Unpacking publicsuffix (20250108.1153-0.1) over (20231001.0357-0.1) ... 135s Preparing to unpack .../093-python3-distro-info_1.13_all.deb ... 136s /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. 136s for fn in glob1(directory, "%s.*" % fname): 136s Unpacking python3-distro-info (1.13) over (1.12) ... 136s Preparing to unpack .../094-python3.13-gdbm_3.13.2-1_armhf.deb ... 136s Unpacking python3.13-gdbm (3.13.2-1) over (3.13.0-2) ... 136s Preparing to unpack .../095-python3.12-gdbm_3.12.9-1_armhf.deb ... 136s Unpacking python3.12-gdbm (3.12.9-1) over (3.12.7-3) ... 136s Preparing to unpack .../096-python3-gdbm_3.13.1-1_armhf.deb ... 136s Unpacking python3-gdbm:armhf (3.13.1-1) over (3.12.7-1) ... 136s Preparing to unpack .../097-telnet_0.17+2.5-6ubuntu1_all.deb ... 136s Unpacking telnet (0.17+2.5-6ubuntu1) over (0.17+2.5-5ubuntu1) ... 136s Preparing to unpack .../098-ubuntu-standard_1.547_armhf.deb ... 136s Unpacking ubuntu-standard (1.547) over (1.544) ... 136s Preparing to unpack .../099-ufw_0.36.2-9_all.deb ... 136s /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. 136s for fn in glob1(directory, "%s.*" % fname): 136s Unpacking ufw (0.36.2-9) over (0.36.2-8) ... 136s Preparing to unpack .../100-usb.ids_2025.01.14-1_all.deb ... 136s Unpacking usb.ids (2025.01.14-1) over (2024.07.04-1) ... 136s Preparing to unpack .../101-xauth_1%3a1.1.2-1.1_armhf.deb ... 136s Unpacking xauth (1:1.1.2-1.1) over (1:1.1.2-1build1) ... 136s Preparing to unpack .../102-appstream_1.0.4-1_armhf.deb ... 136s Unpacking appstream (1.0.4-1) over (1.0.3-1) ... 136s Preparing to unpack .../103-libctf0_2.44-2ubuntu1_armhf.deb ... 136s Unpacking libctf0:armhf (2.44-2ubuntu1) over (2.43.1-4ubuntu1) ... 136s Preparing to unpack .../104-libctf-nobfd0_2.44-2ubuntu1_armhf.deb ... 136s Unpacking libctf-nobfd0:armhf (2.44-2ubuntu1) over (2.43.1-4ubuntu1) ... 136s Preparing to unpack .../105-binutils-arm-linux-gnueabihf_2.44-2ubuntu1_armhf.deb ... 136s Unpacking binutils-arm-linux-gnueabihf (2.44-2ubuntu1) over (2.43.1-4ubuntu1) ... 136s Preparing to unpack .../106-libbinutils_2.44-2ubuntu1_armhf.deb ... 136s Unpacking libbinutils:armhf (2.44-2ubuntu1) over (2.43.1-4ubuntu1) ... 136s Preparing to unpack .../107-binutils_2.44-2ubuntu1_armhf.deb ... 136s Unpacking binutils (2.44-2ubuntu1) over (2.43.1-4ubuntu1) ... 136s Preparing to unpack .../108-binutils-common_2.44-2ubuntu1_armhf.deb ... 136s Unpacking binutils-common:armhf (2.44-2ubuntu1) over (2.43.1-4ubuntu1) ... 136s Preparing to unpack .../109-libsframe1_2.44-2ubuntu1_armhf.deb ... 136s Unpacking libsframe1:armhf (2.44-2ubuntu1) over (2.43.1-4ubuntu1) ... 136s Preparing to unpack .../110-btrfs-progs_6.12-1build1_armhf.deb ... 136s Unpacking btrfs-progs (6.12-1build1) over (6.6.3-1.2) ... 137s Preparing to unpack .../111-python3-certifi_2025.1.31+ds-1_all.deb ... 137s /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. 137s for fn in glob1(directory, "%s.*" % fname): 137s Unpacking python3-certifi (2025.1.31+ds-1) over (2024.8.30+dfsg-1) ... 137s Preparing to unpack .../112-python3-chardet_5.2.0+dfsg-2_all.deb ... 137s /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. 137s for fn in glob1(directory, "%s.*" % fname): 137s Unpacking python3-chardet (5.2.0+dfsg-2) over (5.2.0+dfsg-1) ... 137s Preparing to unpack .../113-python3-idna_3.10-1_all.deb ... 137s /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. 137s for fn in glob1(directory, "%s.*" % fname): 137s Unpacking python3-idna (3.10-1) over (3.8-2) ... 137s Preparing to unpack .../114-python3-urllib3_2.3.0-1_all.deb ... 137s /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. 137s for fn in glob1(directory, "%s.*" % fname): 137s Unpacking python3-urllib3 (2.3.0-1) over (2.0.7-2ubuntu0.1) ... 137s Preparing to unpack .../115-python3-requests_2.32.3+dfsg-4ubuntu1_all.deb ... 137s /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. 137s for fn in glob1(directory, "%s.*" % fname): 137s Unpacking python3-requests (2.32.3+dfsg-4ubuntu1) over (2.32.3+dfsg-1ubuntu1) ... 137s Preparing to unpack .../116-python3-jinja2_3.1.5-2_all.deb ... 137s /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. 137s for fn in glob1(directory, "%s.*" % fname): 137s Unpacking python3-jinja2 (3.1.5-2) over (3.1.3-1ubuntu1) ... 137s Preparing to unpack .../117-python3-json-pointer_2.4-3_all.deb ... 137s /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. 137s for fn in glob1(directory, "%s.*" % fname): 137s Unpacking python3-json-pointer (2.4-3) over (2.4-2) ... 137s Preparing to unpack .../118-python3-jsonpatch_1.32-5_all.deb ... 137s /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. 137s for fn in glob1(directory, "%s.*" % fname): 137s Unpacking python3-jsonpatch (1.32-5) over (1.32-4) ... 138s Preparing to unpack .../119-python3-attr_25.1.0-1_all.deb ... 138s /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. 138s for fn in glob1(directory, "%s.*" % fname): 138s Unpacking python3-attr (25.1.0-1) over (23.2.0-2) ... 138s Preparing to unpack .../120-python3-referencing_0.35.1-2ubuntu1_all.deb ... 138s /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. 138s for fn in glob1(directory, "%s.*" % fname): 138s Unpacking python3-referencing (0.35.1-2ubuntu1) over (0.35.1-1ubuntu1) ... 138s Preparing to unpack .../121-python3-jsonschema_4.19.2-6ubuntu1_all.deb ... 138s /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. 138s for fn in glob1(directory, "%s.*" % fname): 138s Unpacking python3-jsonschema (4.19.2-6ubuntu1) over (4.19.2-3ubuntu1) ... 138s Preparing to unpack .../122-python3-jwt_2.10.1-2_all.deb ... 138s /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. 138s for fn in glob1(directory, "%s.*" % fname): 138s Unpacking python3-jwt (2.10.1-2) over (2.7.0-1) ... 138s Preparing to unpack .../123-python3-oauthlib_3.2.2-3_all.deb ... 138s /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. 138s for fn in glob1(directory, "%s.*" % fname): 138s Unpacking python3-oauthlib (3.2.2-3) over (3.2.2-2) ... 138s Preparing to unpack .../124-cloud-init-base_25.1-0ubuntu1_all.deb ... 138s /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. 138s for fn in glob1(directory, "%s.*" % fname): 138s Unpacking cloud-init-base (25.1-0ubuntu1) over (24.4-0ubuntu1) ... 139s dpkg: warning: unable to delete old directory '/lib/systemd/system/sshd-keygen@.service.d': Directory not empty 139s Preparing to unpack .../125-cryptsetup-bin_2%3a2.7.5-1ubuntu2_armhf.deb ... 139s Unpacking cryptsetup-bin (2:2.7.5-1ubuntu2) over (2:2.7.2-2ubuntu1) ... 139s Preparing to unpack .../126-curl_8.12.0+git20250209.89ed161+ds-1ubuntu1_armhf.deb ... 139s Unpacking curl (8.12.0+git20250209.89ed161+ds-1ubuntu1) over (8.11.0-1ubuntu2) ... 139s Preparing to unpack .../127-libcurl4t64_8.12.0+git20250209.89ed161+ds-1ubuntu1_armhf.deb ... 139s Unpacking libcurl4t64:armhf (8.12.0+git20250209.89ed161+ds-1ubuntu1) over (8.11.0-1ubuntu2) ... 139s Preparing to unpack .../128-dpkg-dev_1.22.11ubuntu4_all.deb ... 139s Unpacking dpkg-dev (1.22.11ubuntu4) over (1.22.11ubuntu3) ... 139s Preparing to unpack .../129-libdpkg-perl_1.22.11ubuntu4_all.deb ... 139s Unpacking libdpkg-perl (1.22.11ubuntu4) over (1.22.11ubuntu3) ... 139s Preparing to unpack .../130-make_4.4.1-1_armhf.deb ... 139s Unpacking make (4.4.1-1) over (4.3-4.1build2) ... 139s Preparing to unpack .../131-lto-disabled-list_56_all.deb ... 139s Unpacking lto-disabled-list (56) over (54) ... 139s Preparing to unpack .../132-libarchive13t64_3.7.7-0ubuntu1_armhf.deb ... 139s Unpacking libarchive13t64:armhf (3.7.7-0ubuntu1) over (3.7.4-1.1) ... 139s Preparing to unpack .../133-libjson-glib-1.0-common_1.10.6+ds-1_all.deb ... 139s Unpacking libjson-glib-1.0-common (1.10.6+ds-1) over (1.10.0+ds-3) ... 139s Preparing to unpack .../134-libjson-glib-1.0-0_1.10.6+ds-1_armhf.deb ... 139s Unpacking libjson-glib-1.0-0:armhf (1.10.6+ds-1) over (1.10.0+ds-3) ... 139s Preparing to unpack .../135-fwupd_2.0.6-3_armhf.deb ... 139s Unpacking fwupd (2.0.6-3) over (2.0.2-1) ... 140s Preparing to unpack .../136-libfwupd3_2.0.6-3_armhf.deb ... 140s Unpacking libfwupd3:armhf (2.0.6-3) over (2.0.2-1) ... 140s Preparing to unpack .../137-libprotobuf-c1_1.5.1-1ubuntu1_armhf.deb ... 140s Unpacking libprotobuf-c1:armhf (1.5.1-1ubuntu1) over (1.4.1-1ubuntu4) ... 140s Preparing to unpack .../138-libqmi-proxy_1.35.6-1_armhf.deb ... 140s Unpacking libqmi-proxy (1.35.6-1) over (1.35.2-0ubuntu2) ... 140s Preparing to unpack .../139-libqmi-glib5_1.35.6-1_armhf.deb ... 140s Unpacking libqmi-glib5:armhf (1.35.6-1) over (1.35.2-0ubuntu2) ... 140s Preparing to unpack .../140-gir1.2-packagekitglib-1.0_1.3.0-3build1_armhf.deb ... 140s Unpacking gir1.2-packagekitglib-1.0 (1.3.0-3build1) over (1.3.0-2) ... 140s Preparing to unpack .../141-gnupg-l10n_2.4.4-2ubuntu22_all.deb ... 140s Unpacking gnupg-l10n (2.4.4-2ubuntu22) over (2.4.4-2ubuntu18) ... 140s Preparing to unpack .../142-htop_3.3.0-5_armhf.deb ... 140s Unpacking htop (3.3.0-5) over (3.3.0-4build1) ... 140s Preparing to unpack .../143-libblockdev-utils3_3.3.0-1_armhf.deb ... 140s Unpacking libblockdev-utils3:armhf (3.3.0-1) over (3.2.1-1) ... 140s Preparing to unpack .../144-libnspr4_2%3a4.36-1ubuntu1_armhf.deb ... 140s Unpacking libnspr4:armhf (2:4.36-1ubuntu1) over (2:4.35-1.1ubuntu2) ... 140s Preparing to unpack .../145-libnss3_2%3a3.108-1ubuntu1_armhf.deb ... 140s Unpacking libnss3:armhf (2:3.108-1ubuntu1) over (2:3.103-1) ... 140s Preparing to unpack .../146-libgpgme11t64_1.24.2-1ubuntu1_armhf.deb ... 140s Unpacking libgpgme11t64:armhf (1.24.2-1ubuntu1) over (1.24.0-2ubuntu1) ... 140s Preparing to unpack .../147-libvolume-key1_0.3.12-9_armhf.deb ... 140s Unpacking libvolume-key1:armhf (0.3.12-9) over (0.3.12-8) ... 140s Preparing to unpack .../148-libblockdev-crypto3_3.3.0-1_armhf.deb ... 140s Unpacking libblockdev-crypto3:armhf (3.3.0-1) over (3.2.1-1) ... 140s Preparing to unpack .../149-libblockdev-fs3_3.3.0-1_armhf.deb ... 140s Unpacking libblockdev-fs3:armhf (3.3.0-1) over (3.2.1-1) ... 140s Preparing to unpack .../150-libblockdev-loop3_3.3.0-1_armhf.deb ... 140s Unpacking libblockdev-loop3:armhf (3.3.0-1) over (3.2.1-1) ... 140s Preparing to unpack .../151-libblockdev-mdraid3_3.3.0-1_armhf.deb ... 140s Unpacking libblockdev-mdraid3:armhf (3.3.0-1) over (3.2.1-1) ... 140s Preparing to unpack .../152-libnvme1t64_1.11.1-2_armhf.deb ... 140s Unpacking libnvme1t64 (1.11.1-2) over (1.11.1-1) ... 140s Preparing to unpack .../153-libblockdev-nvme3_3.3.0-1_armhf.deb ... 140s Unpacking libblockdev-nvme3:armhf (3.3.0-1) over (3.2.1-1) ... 140s Preparing to unpack .../154-libblockdev-part3_3.3.0-1_armhf.deb ... 140s Unpacking libblockdev-part3:armhf (3.3.0-1) over (3.2.1-1) ... 140s Preparing to unpack .../155-libblockdev-swap3_3.3.0-1_armhf.deb ... 140s Unpacking libblockdev-swap3:armhf (3.3.0-1) over (3.2.1-1) ... 141s Preparing to unpack .../156-libblockdev3_3.3.0-1_armhf.deb ... 141s Unpacking libblockdev3:armhf (3.3.0-1) over (3.2.1-1) ... 141s Preparing to unpack .../157-libftdi1-2_1.5-8_armhf.deb ... 141s Unpacking libftdi1-2:armhf (1.5-8) over (1.5-7build1) ... 141s Preparing to unpack .../158-libgudev-1.0-0_1%3a238-6_armhf.deb ... 141s Unpacking libgudev-1.0-0:armhf (1:238-6) over (1:238-5ubuntu1) ... 141s Selecting previously unselected package libicu76:armhf. 141s Preparing to unpack .../159-libicu76_76.1-1ubuntu2_armhf.deb ... 141s Unpacking libicu76:armhf (76.1-1ubuntu2) ... 141s Preparing to unpack .../160-libsasl2-modules_2.1.28+dfsg1-8build1_armhf.deb ... 141s Unpacking libsasl2-modules:armhf (2.1.28+dfsg1-8build1) over (2.1.28+dfsg1-8) ... 141s Preparing to unpack .../161-udisks2_2.10.1-11ubuntu2_armhf.deb ... 141s Unpacking udisks2 (2.10.1-11ubuntu2) over (2.10.1-11ubuntu1) ... 141s Preparing to unpack .../162-libudisks2-0_2.10.1-11ubuntu2_armhf.deb ... 141s Unpacking libudisks2-0:armhf (2.10.1-11ubuntu2) over (2.10.1-11ubuntu1) ... 141s Preparing to unpack .../163-libwrap0_7.6.q-35_armhf.deb ... 141s Unpacking libwrap0:armhf (7.6.q-35) over (7.6.q-33) ... 141s Selecting previously unselected package linux-headers-6.12.0-15. 141s Preparing to unpack .../164-linux-headers-6.12.0-15_6.12.0-15.15_all.deb ... 141s Unpacking linux-headers-6.12.0-15 (6.12.0-15.15) ... 144s Selecting previously unselected package linux-headers-6.12.0-15-generic. 144s Preparing to unpack .../165-linux-headers-6.12.0-15-generic_6.12.0-15.15_armhf.deb ... 144s Unpacking linux-headers-6.12.0-15-generic (6.12.0-15.15) ... 146s Preparing to unpack .../166-linux-headers-generic_6.12.0-15.15+1_armhf.deb ... 146s Unpacking linux-headers-generic (6.12.0-15.15+1) over (6.11.0-8.8) ... 146s Preparing to unpack .../167-pollinate_4.33-4ubuntu2_all.deb ... 146s Unpacking pollinate (4.33-4ubuntu2) over (4.33-4ubuntu1) ... 146s Preparing to unpack .../168-python3-babel_2.17.0-1_all.deb ... 146s /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. 146s for fn in glob1(directory, "%s.*" % fname): 146s Unpacking python3-babel (2.17.0-1) over (2.16.0-1) ... 146s Preparing to unpack .../169-python-babel-localedata_2.17.0-1_all.deb ... 146s Unpacking python-babel-localedata (2.17.0-1) over (2.16.0-1) ... 146s Preparing to unpack .../170-python3-more-itertools_10.6.0-1_all.deb ... 147s /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. 147s for fn in glob1(directory, "%s.*" % fname): 147s Unpacking python3-more-itertools (10.6.0-1) over (10.5.0-1) ... 147s Preparing to unpack .../171-python3-openssl_25.0.0-1_all.deb ... 147s /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. 147s for fn in glob1(directory, "%s.*" % fname): 147s Unpacking python3-openssl (25.0.0-1) over (24.2.1-1) ... 147s Preparing to unpack .../172-python3-pkg-resources_75.6.0-1_all.deb ... 147s /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. 147s for fn in glob1(directory, "%s.*" % fname): 147s Unpacking python3-pkg-resources (75.6.0-1) over (75.2.0-1) ... 147s Preparing to unpack .../173-python3-setuptools_75.6.0-1_all.deb ... 147s /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. 147s for fn in glob1(directory, "%s.*" % fname): 147s Unpacking python3-setuptools (75.6.0-1) over (75.2.0-1) ... 147s Preparing to unpack .../174-software-properties-common_0.109_all.deb ... 147s /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. 147s for fn in glob1(directory, "%s.*" % fname): 147s Unpacking software-properties-common (0.109) over (0.105) ... 147s Preparing to unpack .../175-python3-software-properties_0.109_all.deb ... 147s /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. 147s for fn in glob1(directory, "%s.*" % fname): 147s Unpacking python3-software-properties (0.109) over (0.105) ... 147s Preparing to unpack .../176-python3-wadllib_2.0.0-2_all.deb ... 148s /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. 148s for fn in glob1(directory, "%s.*" % fname): 148s Unpacking python3-wadllib (2.0.0-2) over (2.0.0-1) ... 148s Preparing to unpack .../177-tmux_3.5a-3_armhf.deb ... 148s Unpacking tmux (3.5a-3) over (3.4-7) ... 148s Preparing to unpack .../178-unattended-upgrades_2.12ubuntu4_all.deb ... 148s Unpacking unattended-upgrades (2.12ubuntu4) over (2.9.1+nmu4ubuntu1) ... 148s dpkg: warning: unable to delete old directory '/lib/systemd/system-sleep': Directory not empty 148s Preparing to unpack .../179-xfsprogs_6.12.0-1ubuntu1_armhf.deb ... 148s Unpacking xfsprogs (6.12.0-1ubuntu1) over (6.8.0-2.2ubuntu2) ... 148s Preparing to unpack .../180-zstd_1.5.6+dfsg-2_armhf.deb ... 148s Unpacking zstd (1.5.6+dfsg-2) over (1.5.6+dfsg-1) ... 148s Preparing to unpack .../181-cloud-init_25.1-0ubuntu1_all.deb ... 148s Unpacking cloud-init (25.1-0ubuntu1) over (24.4-0ubuntu1) ... 148s Preparing to unpack .../182-kpartx_0.9.9-1ubuntu4_armhf.deb ... 148s Unpacking kpartx (0.9.9-1ubuntu4) over (0.9.9-1ubuntu3) ... 148s Preparing to unpack .../183-multipath-tools_0.9.9-1ubuntu4_armhf.deb ... 148s Unpacking multipath-tools (0.9.9-1ubuntu4) over (0.9.9-1ubuntu3) ... 148s Setting up libip4tc2:armhf (1.8.11-2ubuntu1) ... 148s Setting up powermgmt-base (1.38) ... 148s Setting up motd-news-config (13.6ubuntu1) ... 148s Setting up distro-info (1.13) ... 148s Setting up liburcu8t64:armhf (0.15.1-1) ... 148s Setting up libibverbs1:armhf (55.0-1ubuntu1) ... 148s Setting up libxdmcp6:armhf (1:1.1.5-1) ... 148s Setting up lto-disabled-list (56) ... 148s Setting up pci.ids (0.0~2025.02.12-1) ... 148s Setting up libnewt0.52:armhf (0.52.24-4ubuntu1) ... 148s Setting up apt-utils (2.9.30ubuntu1) ... 148s Setting up bsdextrautils (2.40.2-14ubuntu1) ... 148s Setting up init (1.68) ... 148s Setting up ibverbs-providers:armhf (55.0-1ubuntu1) ... 148s Setting up gcc-14-base:armhf (14.2.0-17ubuntu3) ... 148s Setting up psmisc (23.7-2) ... 148s Setting up libcbor0.10:armhf (0.10.2-2ubuntu1) ... 148s Setting up libyaml-0-2:armhf (0.2.5-2) ... 148s Setting up libip6tc2:armhf (1.8.11-2ubuntu1) ... 148s Setting up liblsof0 (4.99.4+dfsg-2) ... 148s Setting up libmaxminddb0:armhf (1.12.2-1) ... 148s Setting up python3.12-gdbm (3.12.9-1) ... 148s Setting up libedit2:armhf (3.1-20250104-1) ... 148s Setting up libsasl2-modules:armhf (2.1.28+dfsg1-8build1) ... 148s Setting up netcat-openbsd (1.228-1) ... 148s Setting up libpython3.12-minimal:armhf (3.12.9-1) ... 148s Setting up binutils-common:armhf (2.44-2ubuntu1) ... 148s Setting up libctf-nobfd0:armhf (2.44-2ubuntu1) ... 148s Setting up gettext-base (0.23.1-1) ... 148s Setting up libnss-systemd:armhf (257.2-3ubuntu1) ... 148s Setting up libnftnl11:armhf (1.2.8-1) ... 148s Setting up krb5-locales (1.21.3-4ubuntu1) ... 148s Setting up libcom-err2:armhf (1.47.2-1ubuntu1) ... 148s Setting up libjemalloc2:armhf (5.3.0-2build1) ... 148s Setting up lshw (02.19.git.2021.06.19.996aaad9c7-2.1ubuntu1) ... 148s Setting up locales (2.40-4ubuntu1) ... 149s Generating locales (this might take a while)... 151s en_US.UTF-8... done 151s Generation complete. 151s Setting up libldap-common (2.6.9+dfsg-1~exp2ubuntu1) ... 151s Installing new version of config file /etc/ldap/ldap.conf ... 151s Setting up libprotobuf-c1:armhf (1.5.1-1ubuntu1) ... 151s Setting up xxd (2:9.1.0967-1ubuntu2) ... 151s Setting up libsframe1:armhf (2.44-2ubuntu1) ... 151s Setting up python-babel-localedata (2.17.0-1) ... 151s Setting up libkrb5support0:armhf (1.21.3-4ubuntu1) ... 151s Setting up libsasl2-modules-db:armhf (2.1.28+dfsg1-8build1) ... 151s Setting up tzdata (2025a-2ubuntu1) ... 151s 151s Current default time zone: 'Etc/UTC' 151s Local time is now: Sat Feb 22 05:04:31 UTC 2025. 151s Universal Time is now: Sat Feb 22 05:04:31 UTC 2025. 151s Run 'dpkg-reconfigure tzdata' if you wish to change it. 151s 151s Setting up eject (2.40.2-14ubuntu1) ... 151s Setting up apparmor (4.1.0~beta5-0ubuntu5) ... 151s Installing new version of config file /etc/apparmor.d/abstractions/dconf ... 151s Installing new version of config file /etc/apparmor.d/abstractions/mesa ... 151s Installing new version of config file /etc/apparmor.d/abstractions/nameservice ... 151s Installing new version of config file /etc/apparmor.d/abstractions/php ... 151s Installing new version of config file /etc/apparmor.d/abstractions/python ... 151s Installing new version of config file /etc/apparmor.d/sbuild ... 151s Installing new version of config file /etc/apparmor.d/sbuild-abort ... 151s Installing new version of config file /etc/apparmor.d/sbuild-adduser ... 151s Installing new version of config file /etc/apparmor.d/sbuild-apt ... 151s Installing new version of config file /etc/apparmor.d/sbuild-checkpackages ... 151s Installing new version of config file /etc/apparmor.d/sbuild-clean ... 151s Installing new version of config file /etc/apparmor.d/sbuild-createchroot ... 151s Installing new version of config file /etc/apparmor.d/sbuild-destroychroot ... 151s Installing new version of config file /etc/apparmor.d/sbuild-distupgrade ... 151s Installing new version of config file /etc/apparmor.d/sbuild-hold ... 151s Installing new version of config file /etc/apparmor.d/sbuild-shell ... 151s Installing new version of config file /etc/apparmor.d/sbuild-unhold ... 151s Installing new version of config file /etc/apparmor.d/sbuild-update ... 151s Installing new version of config file /etc/apparmor.d/sbuild-upgrade ... 151s Installing new version of config file /etc/apparmor.d/slirp4netns ... 151s Installing new version of config file /etc/apparmor.d/toybox ... 151s Installing new version of config file /etc/apparmor.d/transmission ... 151s Installing new version of config file /etc/apparmor.d/tunables/global ... 151s apparmor_parser: Unable to replace "lsb_release". apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 151s 151s apparmor_parser: Unable to replace "kmod". apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 151s 151s apparmor_parser: Unable to replace "nvidia_modprobe". apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 151s 152s Reloading AppArmor profiles 152s /sbin/apparmor_parser: Unable to replace "1password". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "Discord". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "MongoDB Compass". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "QtWebEngineProcess". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "balena-etcher". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "brave". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "buildah". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "busybox". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "ch-checkns". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "bwrap". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "babeld". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "cam". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "ch-run". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "chrome". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "crun". /sbin/apparmor_parser: Unable to replace "vscode". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "chromium". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "bfdd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "devhelp". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "alsamixer". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "element-desktop". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "epiphany". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "evolution". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "firefox". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "flatpak". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "foliate". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "geary". /sbin/apparmor_parser: Unable to replace "bgpd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "github-desktop". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "goldendict". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "dnstracer". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "ipa_verify". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "kchmviewer". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "fabricd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "keybase". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "eigrpd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "lc-compliance". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "fusermount3". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "libcamerify". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "loupe". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "Xorg". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "linux-sandbox". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "lxc-attach". /sbin/apparmor_parser: Unable to replace "iotop-c". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "lxc-create". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "lxc-destroy". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "isisd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "lxc-execute". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "ldpd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "lxc-stop". /sbin/apparmor_parser: Unable to replace "lxc-unshare". /sbin/apparmor_parser: Unable to replace "lxc-usernsexec". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "mmdebstrap". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "msedge". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "lsblk". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "nautilus". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "notepadqq". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "lsusb". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "lsb_release". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "opam". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "obsidian". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "opera". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "mosquitto". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "irssi". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "pageedit". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "kmod". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "nvidia_modprobe". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "nc.openbsd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "mbsync". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "nhrpd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "pathd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "podman". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "pbrd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "pim6d". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "polypane". /sbin/apparmor_parser: Unable to replace "privacybrowser". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "qcam". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "qmapshack". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "ospf6d". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "qutebrowser". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "QtWebEngineProcess". /sbin/apparmor_parser: Unable to replace "ospfd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "plasmashell". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "rootlesskit". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "rpm". /sbin/apparmor_parser: Unable to replace "pimd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "rssguard". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "runc". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "ip". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "openvpn". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild-abort". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild-apt". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild-adduser". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild-checkpackages". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild-clean". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild-createchroot". /sbin/apparmor_parser: Unable to replace "sbuild-destroychroot". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild-hold". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild-distupgrade". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "ripngd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "scide". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild-shell". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "ripd". /sbin/apparmor_parser: Unable to replace "sbuild-unhold". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild-upgrade". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "signal-desktop". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "sbuild-update". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "stress-ng". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "steam". /sbin/apparmor_parser: Unable to replace "slirp4netns". /sbin/apparmor_parser: Unable to replace "systemd-coredump". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "slack". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "surfshark". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "thunderbird". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "toybox". /sbin/apparmor_parser: Unable to replace "trinity". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "tup". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "staticd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "tuxedo-control-center". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "tinyproxy". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "ubuntu_pro_apt_news". /sbin/apparmor_parser: Unable to replace "mx-extract". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "rygel". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "unprivileged_userns". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "userbindmount". /sbin/apparmor_parser: Unable to replace "unpriv_unshare". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 152s /sbin/apparmor_parser: Unable to replace "unix-chkpwd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 152s 153s /sbin/apparmor_parser: Unable to replace "/usr/bin/man". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "uwsgi-core". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "vdens". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "cmds". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "tnftp". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "virtiofsd". /sbin/apparmor_parser: Unable to replace "vivaldi-bin". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "vpnns". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "vrrpd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "dumpcap". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "tshark". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "wike". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "wg". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "rsyslogd". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "remmina". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "wpcom". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "znc". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "ip". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "wg-quick". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "tcpdump". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "transmission-cli". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "apt_methods". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s /sbin/apparmor_parser: Unable to replace "ubuntu_pro_esm_cache". /sbin/apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 153s 153s Error: At least one profile failed to load 153s Setting up libglib2.0-data (2.83.4-1) ... 153s Setting up vim-common (2:9.1.0967-1ubuntu2) ... 153s Setting up busybox-static (1:1.37.0-4ubuntu1) ... 153s Setting up libwrap0:armhf (7.6.q-35) ... 153s Setting up libnvme1t64 (1.11.1-2) ... 153s Setting up make (4.4.1-1) ... 153s Setting up libnspr4:armhf (2:4.36-1ubuntu1) ... 153s Setting up gnupg-l10n (2.4.4-2ubuntu22) ... 153s Setting up ed (1.21-1) ... 153s Setting up bash-completion (1:2.16.0-7) ... 153s Setting up libncurses6:armhf (6.5+20250125-2) ... 153s Setting up libdbus-1-3:armhf (1.16.0-1ubuntu1) ... 153s Setting up libfribidi0:armhf (1.0.16-1) ... 153s Setting up libpng16-16t64:armhf (1.6.46-4) ... 153s Setting up systemd-timesyncd (257.2-3ubuntu1) ... 153s systemd-time-wait-sync.service is a disabled or a static unit not running, not starting it. 153s Setting up libatomic1:armhf (15-20250213-1ubuntu1) ... 153s Setting up udev (257.2-3ubuntu1) ... 154s Setting up libss2:armhf (1.47.2-1ubuntu1) ... 154s Setting up usb.ids (2025.01.14-1) ... 154s Setting up dhcpcd-base (1:10.1.0-7) ... 154s Installing new version of config file /etc/dhcpcd.conf ... 154s Setting up ucf (3.0050) ... 154s Installing new version of config file /etc/ucf.conf ... 154s Setting up libncursesw6:armhf (6.5+20250125-2) ... 154s Setting up libk5crypto3:armhf (1.21.3-4ubuntu1) ... 154s Setting up busybox-initramfs (1:1.37.0-4ubuntu1) ... 154s Setting up libxtables12:armhf (1.8.11-2ubuntu1) ... 154s Setting up logsave (1.47.2-1ubuntu1) ... 154s Setting up libsasl2-2:armhf (2.1.28+dfsg1-8build1) ... 154s Setting up lsof (4.99.4+dfsg-2) ... 154s Setting up libfdisk1:armhf (2.40.2-14ubuntu1) ... 154s Setting up libicu74:armhf (74.2-1ubuntu6) ... 154s Setting up nano (8.3-1) ... 154s Installing new version of config file /etc/nanorc ... 154s Setting up libdevmapper1.02.1:armhf (2:1.02.201-1ubuntu1) ... 154s Setting up whiptail (0.52.24-4ubuntu1) ... 154s Setting up python-apt-common (2.9.9) ... 154s Setting up dracut-install (106-2ubuntu1) ... 154s Setting up perl-modules-5.40 (5.40.1-2) ... 154s Setting up dmsetup (2:1.02.201-1ubuntu1) ... 154s Setting up uuid-runtime (2.40.2-14ubuntu1) ... 155s uuidd.service is a disabled or a static unit not running, not starting it. 155s Setting up xauth (1:1.1.2-1.1) ... 155s Setting up groff-base (1.23.0-7) ... 155s Setting up libtraceevent1:armhf (1:1.8.4-2) ... 155s Setting up dbus-session-bus-common (1.16.0-1ubuntu1) ... 155s Setting up kpartx (0.9.9-1ubuntu4) ... 155s Setting up libpcap0.8t64:armhf (1.10.5-2ubuntu1) ... 155s Setting up libcryptsetup12:armhf (2:2.7.5-1ubuntu2) ... 155s Setting up libjson-glib-1.0-common (1.10.6+ds-1) ... 155s Setting up mawk (1.3.4.20250131-1) ... 155s Setting up libkrb5-3:armhf (1.21.3-4ubuntu1) ... 155s Setting up libusb-1.0-0:armhf (2:1.0.27-2) ... 155s Setting up libicu76:armhf (76.1-1ubuntu2) ... 155s Setting up linux-headers-6.12.0-15 (6.12.0-15.15) ... 155s Setting up keyboard-configuration (1.226ubuntu3) ... 156s Your console font configuration will be updated the next time your system 156s boots. If you want to update it now, run 'setupcon' from a virtual console. 156s update-initramfs: deferring update (trigger activated) 156s Setting up libbinutils:armhf (2.44-2ubuntu1) ... 156s Setting up dbus-system-bus-common (1.16.0-1ubuntu1) ... 156s Setting up openssl (3.4.1-1ubuntu1) ... 156s Installing new version of config file /etc/ssl/openssl.cnf ... 156s Setting up libgpg-error-l10n (1.51-3) ... 156s Setting up iputils-ping (3:20240905-1ubuntu1) ... 156s Setting up readline-common (8.2-6) ... 156s Setting up publicsuffix (20250108.1153-0.1) ... 156s Setting up libxml2:armhf (2.12.7+dfsg+really2.9.14-0.2ubuntu3) ... 156s Setting up tmux (3.5a-3) ... 156s Setting up zstd (1.5.6+dfsg-2) ... 156s Setting up libldap2:armhf (2.6.9+dfsg-1~exp2ubuntu1) ... 156s Setting up dbus-bin (1.16.0-1ubuntu1) ... 156s Setting up libbpf1:armhf (1:1.5.0-2) ... 156s Setting up iputils-tracepath (3:20240905-1ubuntu1) ... 156s Setting up rsync (3.4.1-0syncable1) ... 157s rsync.service is a disabled or a static unit not running, not starting it. 157s Setting up python3.13-gdbm (3.13.2-1) ... 157s Setting up ethtool (1:6.11-1) ... 157s Setting up gnupg-utils (2.4.4-2ubuntu22) ... 157s Setting up initramfs-tools-bin (0.145ubuntu2) ... 157s Setting up ncurses-term (6.5+20250125-2) ... 157s Setting up login (1:4.16.0-2+really2.40.2-14ubuntu1) ... 157s Setting up cron-daemon-common (3.0pl1-192ubuntu1) ... 157s Setting up libxkbcommon0:armhf (1.7.0-2) ... 157s Setting up libctf0:armhf (2.44-2ubuntu1) ... 157s Setting up cryptsetup-bin (2:2.7.5-1ubuntu2) ... 157s Setting up pinentry-curses (1.3.1-2ubuntu2) ... 157s Setting up python3.12-minimal (3.12.9-1) ... 158s Setting up libnftables1:armhf (1.1.1-1build1) ... 158s Setting up nftables (1.1.1-1build1) ... 159s Setting up iptables (1.8.11-2ubuntu1) ... 159s Setting up htop (3.3.0-5) ... 159s Setting up iproute2 (6.13.0-1ubuntu1) ... 159s Setting up btrfs-progs (6.12-1build1) ... 159s Setting up cron (3.0pl1-192ubuntu1) ... 160s Setting up rsyslog (8.2412.0-2ubuntu1) ... 160s Installing new version of config file /etc/apparmor.d/usr.sbin.rsyslogd ... 160s info: The user `syslog' is already a member of `adm'. 160s apparmor_parser: Unable to replace "rsyslogd". apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 160s 161s Setting up inetutils-telnet (2:2.5-6ubuntu1) ... 161s Setting up e2fsprogs (1.47.2-1ubuntu1) ... 161s update-initramfs: deferring update (trigger activated) 161s Setting up libnss3:armhf (2:3.108-1ubuntu1) ... 161s Setting up dbus-daemon (1.16.0-1ubuntu1) ... 161s Setting up vim-tiny (2:9.1.0967-1ubuntu2) ... 161s Setting up multipath-tools (0.9.9-1ubuntu4) ... 162s Setting up libperl5.40:armhf (5.40.1-2) ... 162s Setting up libftdi1-2:armhf (1.5-8) ... 162s Setting up ca-certificates (20241223) ... 165s Updating certificates in /etc/ssl/certs... 166s rehash: warning: skipping ca-certificates.crt, it does not contain exactly one certificate or CRL 166s 7 added, 1 removed; done. 166s Setting up perl (5.40.1-2) ... 166s Setting up libglib2.0-0t64:armhf (2.83.4-1) ... 166s No schema files found: doing nothing. 166s Setting up systemd-cryptsetup (257.2-3ubuntu1) ... 166s Setting up dbus (1.16.0-1ubuntu1) ... 166s A reboot is required to replace the running dbus-daemon. 166s Please reboot the system when convenient. 167s Setting up libblockdev-utils3:armhf (3.3.0-1) ... 167s Setting up linux-headers-6.12.0-15-generic (6.12.0-15.15) ... 167s Setting up libgssapi-krb5-2:armhf (1.21.3-4ubuntu1) ... 167s Setting up gir1.2-glib-2.0:armhf (2.83.4-1) ... 167s Setting up libdpkg-perl (1.22.11ubuntu4) ... 167s Setting up libreadline8t64:armhf (8.2-6) ... 167s Setting up libblockdev-nvme3:armhf (3.3.0-1) ... 167s Setting up libblockdev-fs3:armhf (3.3.0-1) ... 167s Setting up libtraceevent1-plugin:armhf (1:1.8.4-2) ... 167s Setting up libplymouth5:armhf (24.004.60-2ubuntu5) ... 167s Setting up gpgconf (2.4.4-2ubuntu22) ... 167s Setting up libpam-systemd:armhf (257.2-3ubuntu1) ... 167s Setting up libgirepository-1.0-1:armhf (1.82.0-4) ... 167s Setting up initramfs-tools-core (0.145ubuntu2) ... 167s Setting up binutils-arm-linux-gnueabihf (2.44-2ubuntu1) ... 167s Setting up libarchive13t64:armhf (3.7.7-0ubuntu1) ... 167s Setting up libpython3.13-stdlib:armhf (3.13.2-1) ... 167s Setting up gpg (2.4.4-2ubuntu22) ... 167s Setting up libgudev-1.0-0:armhf (1:238-6) ... 167s Setting up libpolkit-gobject-1-0:armhf (126-2) ... 167s Setting up libgstreamer1.0-0:armhf (1.25.50-1) ... 167s Setcap worked! gst-ptp-helper is not suid! 167s Setting up libudisks2-0:armhf (2.10.1-11ubuntu2) ... 167s Setting up libpython3-stdlib:armhf (3.13.1-1~exp2) ... 167s Setting up systemd-resolved (257.2-3ubuntu1) ... 167s Setting up gpg-agent (2.4.4-2ubuntu22) ... 168s Setting up telnet (0.17+2.5-6ubuntu1) ... 168s Setting up libpython3.12-stdlib:armhf (3.12.9-1) ... 168s Setting up initramfs-tools (0.145ubuntu2) ... 168s update-initramfs: deferring update (trigger activated) 168s Setting up libblockdev-mdraid3:armhf (3.3.0-1) ... 168s Setting up libcurl4t64:armhf (8.12.0+git20250209.89ed161+ds-1ubuntu1) ... 168s Setting up bind9-libs:armhf (1:9.20.4-3ubuntu1) ... 168s Setting up e2fsprogs-l10n (1.47.2-1ubuntu1) ... 168s Setting up python3.13 (3.13.2-1) ... 169s Setting up libblockdev-swap3:armhf (3.3.0-1) ... 169s Setting up plymouth (24.004.60-2ubuntu5) ... 169s update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults 169s update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults 169s Setting up python3.12 (3.12.9-1) ... 171s Setting up libblockdev-loop3:armhf (3.3.0-1) ... 171s Setting up gpgsm (2.4.4-2ubuntu22) ... 171s Setting up libcurl3t64-gnutls:armhf (8.12.0+git20250209.89ed161+ds-1ubuntu1) ... 171s Setting up libglib2.0-bin (2.83.4-1) ... 171s Setting up libpackagekit-glib2-18:armhf (1.3.0-3build1) ... 171s Setting up libappstream5:armhf (1.0.4-1) ... 171s Setting up libqmi-glib5:armhf (1.35.6-1) ... 171s Setting up python3 (3.13.1-1~exp2) ... 171s /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. 171s for fn in glob1(directory, "%s.*" % fname): 171s Setting up linux-headers-generic (6.12.0-15.15+1) ... 171s Setting up binutils (2.44-2ubuntu1) ... 171s Setting up libnetplan1:armhf (1.1.2-2ubuntu1) ... 171s Setting up python3-newt:armhf (0.52.24-4ubuntu1) ... 171s Setting up libblockdev3:armhf (3.3.0-1) ... 171s Setting up fdisk (2.40.2-14ubuntu1) ... 171s Setting up dpkg-dev (1.22.11ubuntu4) ... 171s Setting up libjson-glib-1.0-0:armhf (1.10.6+ds-1) ... 171s Setting up libblockdev-part3:armhf (3.3.0-1) ... 171s Setting up dirmngr (2.4.4-2ubuntu22) ... 171s Setting up gir1.2-packagekitglib-1.0 (1.3.0-3build1) ... 171s Setting up dbus-user-session (1.16.0-1ubuntu1) ... 171s Setting up python3-jinja2 (3.1.5-2) ... 172s Setting up python3-pygments (2.18.0+dfsg-2) ... 174s Setting up python3-chardet (5.2.0+dfsg-2) ... 174s Setting up appstream (1.0.4-1) ... 176s ✔ Metadata cache was updated successfully. 176s Setting up python3-certifi (2025.1.31+ds-1) ... 176s Setting up gir1.2-girepository-2.0:armhf (1.82.0-4) ... 176s Setting up python3-gi (3.50.0-4) ... 177s Setting up python3-idna (3.10-1) ... 177s Setting up xfsprogs (6.12.0-1ubuntu1) ... 177s update-initramfs: deferring update (trigger activated) 178s Setting up keyboxd (2.4.4-2ubuntu22) ... 178s Setting up python3-urllib3 (2.3.0-1) ... 178s Setting up python3-json-pointer (2.4-3) ... 179s Setting up gnupg (2.4.4-2ubuntu22) ... 179s Setting up python3-netplan (1.1.2-2ubuntu1) ... 179s Setting up libpolkit-agent-1-0:armhf (126-2) ... 179s Setting up libgpgme11t64:armhf (1.24.2-1ubuntu1) ... 179s Setting up curl (8.12.0+git20250209.89ed161+ds-1ubuntu1) ... 179s Setting up libvolume-key1:armhf (0.3.12-9) ... 179s Setting up netplan-generator (1.1.2-2ubuntu1) ... 179s Removing 'diversion of /lib/systemd/system-generators/netplan to /lib/systemd/system-generators/netplan.usr-is-merged by netplan-generator' 179s Setting up bind9-host (1:9.20.4-3ubuntu1) ... 179s Setting up python3-distro-info (1.13) ... 179s Setting up polkitd (126-2) ... 179s Setting up python3-more-itertools (10.6.0-1) ... 179s Setting up python3-attr (25.1.0-1) ... 180s Setting up gpg-wks-client (2.4.4-2ubuntu22) ... 180s Setting up libblockdev-crypto3:armhf (3.3.0-1) ... 180s Setting up python3-jwt (2.10.1-2) ... 180s Setting up python3-babel (2.17.0-1) ... 180s Setting up python3-rich (13.9.4-1) ... 181s Setting up python3-gdbm:armhf (3.13.1-1) ... 181s Setting up python3-problem-report (2.31.0+git20250220-0ubuntu1) ... 181s Setting up python3-apt (2.9.9) ... 181s Setting up python3-jsonpatch (1.32-5) ... 181s Setting up python3-bcrypt (4.2.0-2.1) ... 182s Setting up libqmi-proxy (1.35.6-1) ... 182s Setting up libfwupd3:armhf (2.0.6-3) ... 182s Setting up ufw (0.36.2-9) ... 183s Setting up python3-lazr.uri (1.0.6-5) ... 183s Setting up netplan.io (1.1.2-2ubuntu1) ... 183s Setting up unattended-upgrades (2.12ubuntu4) ... 183s Replacing config file /etc/apt/apt.conf.d/50unattended-upgrades with new version 183s Setting up pollinate (4.33-4ubuntu2) ... 184s Setting up python3-cryptography (43.0.0-1) ... 184s Setting up python3-wadllib (2.0.0-2) ... 184s Setting up python3-requests (2.32.3+dfsg-4ubuntu1) ... 185s Setting up bind9-dnsutils (1:9.20.4-3ubuntu1) ... 185s Setting up ubuntu-pro-client (34.1.3) ... 185s apparmor_parser: Unable to replace "ubuntu_pro_apt_news". apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 185s 185s apparmor_parser: Unable to replace "apt_methods". apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 185s 185s apparmor_parser: Unable to replace "ubuntu_pro_esm_cache". apparmor_parser: Access denied. You need policy admin privileges to manage profiles. 185s 187s Setting up fwupd (2.0.6-3) ... 187s fwupd-refresh.service is a disabled or a static unit not running, not starting it. 187s fwupd.service is a disabled or a static unit not running, not starting it. 187s Setting up python3-referencing (0.35.1-2ubuntu1) ... 187s Setting up python3-pkg-resources (75.6.0-1) ... 188s Setting up ubuntu-pro-client-l10n (34.1.3) ... 188s Setting up udisks2 (2.10.1-11ubuntu2) ... 188s vda: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:01.3/0000:04:00.0/virtio2/block/vda/uevent': Permission denied 188s 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 188s 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 188s 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 188s loop0: Failed to write 'change' to '/sys/devices/virtual/block/loop0/uevent': Permission denied 188s loop1: Failed to write 'change' to '/sys/devices/virtual/block/loop1/uevent': Permission denied 188s loop2: Failed to write 'change' to '/sys/devices/virtual/block/loop2/uevent': Permission denied 188s loop3: Failed to write 'change' to '/sys/devices/virtual/block/loop3/uevent': Permission denied 188s loop4: Failed to write 'change' to '/sys/devices/virtual/block/loop4/uevent': Permission denied 188s loop5: Failed to write 'change' to '/sys/devices/virtual/block/loop5/uevent': Permission denied 188s loop6: Failed to write 'change' to '/sys/devices/virtual/block/loop6/uevent': Permission denied 188s loop7: Failed to write 'change' to '/sys/devices/virtual/block/loop7/uevent': Permission denied 188s loop8: Failed to write 'change' to '/sys/devices/virtual/block/loop8/uevent': Permission denied 188s Setting up python3-setuptools (75.6.0-1) ... 190s Setting up python3-openssl (25.0.0-1) ... 190s Setting up python3-launchpadlib (2.1.0-1) ... 191s Setting up ubuntu-standard (1.547) ... 191s Setting up python3-apport (2.31.0+git20250220-0ubuntu1) ... 191s Setting up python3-oauthlib (3.2.2-3) ... 191s Setting up python3-software-properties (0.109) ... 191s Setting up python3-jsonschema (4.19.2-6ubuntu1) ... 192s Setting up cloud-init-base (25.1-0ubuntu1) ... 192s Installing new version of config file /etc/cloud/templates/sources.list.debian.deb822.tmpl ... 192s Installing new version of config file /etc/cloud/templates/sources.list.ubuntu.deb822.tmpl ... 194s Setting up cloud-init (25.1-0ubuntu1) ... 194s Setting up apport-core-dump-handler (2.31.0+git20250220-0ubuntu1) ... 195s Setting up apport (2.31.0+git20250220-0ubuntu1) ... 195s apport-autoreport.service is a disabled or a static unit not running, not starting it. 196s Setting up kbd (2.7.1-2ubuntu1) ... 196s Setting up console-setup-linux (1.226ubuntu3) ... 197s Setting up console-setup (1.226ubuntu3) ... 198s update-initramfs: deferring update (trigger activated) 198s Setting up ubuntu-minimal (1.547) ... 198s Processing triggers for libc-bin (2.40-4ubuntu1) ... 198s Processing triggers for systemd (257.2-3ubuntu1) ... 198s Processing triggers for man-db (2.13.0-1) ... 199s Processing triggers for shared-mime-info (2.4-5) ... 199s Warning: program compiled against libxml 212 using older 209 200s Processing triggers for sgml-base (1.31) ... 200s Processing triggers for debianutils (5.21) ... 200s Processing triggers for install-info (7.1.1-1) ... 200s Setting up packagekit (1.3.0-3build1) ... 200s Setting up packagekit-tools (1.3.0-3build1) ... 200s Setting up software-properties-common (0.109) ... 200s Processing triggers for initramfs-tools (0.145ubuntu2) ... 200s Setting up plymouth-theme-ubuntu-text (24.004.60-2ubuntu5) ... 200s Processing triggers for ca-certificates (20241223) ... 200s Updating certificates in /etc/ssl/certs... 201s 0 added, 0 removed; done. 201s Running hooks in /etc/ca-certificates/update.d... 201s done. 201s Processing triggers for initramfs-tools (0.145ubuntu2) ... 205s Reading package lists... 205s Building dependency tree... 205s Reading state information... 205s Starting pkgProblemResolver with broken count: 0 205s Starting 2 pkgProblemResolver with broken count: 0 205s Done 206s Solving dependencies... 206s The following packages will be REMOVED: 206s libapt-pkg6.0t64* libassuan0* libicu74* libnsl2* libpython3.12-minimal* 206s libpython3.12-stdlib* libunwind8* linux-headers-6.11.0-8* 206s linux-headers-6.11.0-8-generic* python3.12* python3.12-minimal* 207s 0 upgraded, 0 newly installed, 11 to remove and 0 not upgraded. 207s After this operation, 154 MB disk space will be freed. 207s (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 ... 92815 files and directories currently installed.) 207s Removing libapt-pkg6.0t64:armhf (2.9.29) ... 207s Removing libassuan0:armhf (2.5.6-1build1) ... 207s Removing libicu74:armhf (74.2-1ubuntu6) ... 207s Removing python3.12 (3.12.9-1) ... 207s Removing libpython3.12-stdlib:armhf (3.12.9-1) ... 207s Removing libnsl2:armhf (1.3.0-3build3) ... 207s Removing python3.12-minimal (3.12.9-1) ... 207s /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. 207s for fn in glob1(directory, "%s.%s.py[co]" % (fname, magic_tag)): 208s Removing libpython3.12-minimal:armhf (3.12.9-1) ... 208s Removing libunwind8:armhf (1.6.2-3.1) ... 208s Removing linux-headers-6.11.0-8-generic (6.11.0-8.8) ... 209s Removing linux-headers-6.11.0-8 (6.11.0-8.8) ... 210s Processing triggers for systemd (257.2-3ubuntu1) ... 210s Processing triggers for man-db (2.13.0-1) ... 210s Processing triggers for libc-bin (2.40-4ubuntu1) ... 210s (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 ... 60309 files and directories currently installed.) 210s Purging configuration files for python3.12-minimal (3.12.9-1) ... 210s Purging configuration files for libpython3.12-minimal:armhf (3.12.9-1) ... 212s autopkgtest [05:05:32]: rebooting testbed after setup commands that affected boot 257s autopkgtest [05:06:17]: testbed running kernel: Linux 6.8.0-52-generic #53~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 15 18:10:51 UTC 2 284s autopkgtest [05:06:44]: @@@@@@@@@@@@@@@@@@@@ apt-source libfprint 321s Get:1 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (dsc) [2943 B] 321s Get:2 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (tar) [9291 kB] 321s Get:3 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (diff) [17.8 kB] 322s gpgv: Signature made Thu Feb 20 18:31:16 2025 UTC 322s gpgv: using RSA key D4C501DA48EB797A081750939449C2F50996635F 322s gpgv: Can't check signature: No public key 322s dpkg-source: warning: cannot verify inline signature for ./libfprint_1.94.9+tod1-1.dsc: no acceptable signature found 324s autopkgtest [05:07:24]: testing package libfprint version 1:1.94.9+tod1-1 326s autopkgtest [05:07:26]: build not needed 332s autopkgtest [05:07:32]: test installed-tests: preparing testbed 334s Reading package lists... 335s Building dependency tree... 335s Reading state information... 335s Starting pkgProblemResolver with broken count: 0 335s Starting 2 pkgProblemResolver with broken count: 0 335s Done 336s The following NEW packages will be installed: 336s fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0 336s gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2 336s libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 libfreetype6 336s libgusb2 libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1 336s python3-cairo umockdev 336s 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded. 336s Need to get 9758 kB of archives. 336s After this operation, 32.9 MB of additional disk space will be used. 336s Get:1 http://ftpmaster.internal/ubuntu plucky/main armhf fonts-dejavu-mono all 2.37-8 [502 kB] 337s Get:2 http://ftpmaster.internal/ubuntu plucky/main armhf fonts-dejavu-core all 2.37-8 [835 kB] 337s Get:3 http://ftpmaster.internal/ubuntu plucky/main armhf fontconfig-config armhf 2.15.0-2ubuntu1 [37.5 kB] 337s Get:4 http://ftpmaster.internal/ubuntu plucky/main armhf gir1.2-json-1.0 armhf 1.10.6+ds-1 [9998 B] 337s Get:5 http://ftpmaster.internal/ubuntu plucky/main armhf libgusb2 armhf 0.4.9-1 [34.8 kB] 337s Get:6 http://ftpmaster.internal/ubuntu plucky/main armhf gir1.2-gusb-1.0 armhf 0.4.9-1 [7450 B] 337s Get:7 http://ftpmaster.internal/ubuntu plucky/main armhf libpixman-1-0 armhf 0.44.0-3 [183 kB] 337s Get:8 http://ftpmaster.internal/ubuntu plucky/main armhf libfprint-2-tod1 armhf 1:1.94.9+tod1-1 [58.1 kB] 337s Get:9 http://ftpmaster.internal/ubuntu plucky/main armhf libfprint-2-2 armhf 1:1.94.9+tod1-1 [242 kB] 337s Get:10 http://ftpmaster.internal/ubuntu plucky/main armhf gir1.2-fprint-2.0 armhf 1:1.94.9+tod1-1 [7226 B] 337s Get:11 http://ftpmaster.internal/ubuntu plucky/universe armhf gnome-desktop-testing armhf 2021.1-4 [16.2 kB] 337s Get:12 http://ftpmaster.internal/ubuntu plucky/main armhf libfreetype6 armhf 2.13.3+dfsg-1 [330 kB] 337s Get:13 http://ftpmaster.internal/ubuntu plucky/main armhf libfontconfig1 armhf 2.15.0-2ubuntu1 [114 kB] 337s Get:14 http://ftpmaster.internal/ubuntu plucky/main armhf libxcb-render0 armhf 1.17.0-2 [15.3 kB] 337s Get:15 http://ftpmaster.internal/ubuntu plucky/main armhf libxcb-shm0 armhf 1.17.0-2 [5774 B] 337s Get:16 http://ftpmaster.internal/ubuntu plucky/main armhf libxrender1 armhf 1:0.9.10-1.1build1 [16.0 kB] 337s Get:17 http://ftpmaster.internal/ubuntu plucky/main armhf libcairo2 armhf 1.18.2-2 [484 kB] 337s Get:18 http://ftpmaster.internal/ubuntu plucky/main armhf python3-cairo armhf 1.26.1-2build1 [129 kB] 337s Get:19 http://ftpmaster.internal/ubuntu plucky/universe armhf libumockdev0 armhf 0.19.1-3 [70.2 kB] 337s Get:20 http://ftpmaster.internal/ubuntu plucky/universe armhf umockdev armhf 0.19.1-3 [76.1 kB] 337s Get:21 http://ftpmaster.internal/ubuntu plucky/universe armhf libfprint-2-tests armhf 1:1.94.9+tod1-1 [6584 kB] 338s Fetched 9758 kB in 1s (6593 kB/s) 338s Selecting previously unselected package fonts-dejavu-mono. 338s (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 ... 60307 files and directories currently installed.) 338s Preparing to unpack .../00-fonts-dejavu-mono_2.37-8_all.deb ... 338s Unpacking fonts-dejavu-mono (2.37-8) ... 338s Selecting previously unselected package fonts-dejavu-core. 338s Preparing to unpack .../01-fonts-dejavu-core_2.37-8_all.deb ... 338s Unpacking fonts-dejavu-core (2.37-8) ... 338s Selecting previously unselected package fontconfig-config. 338s Preparing to unpack .../02-fontconfig-config_2.15.0-2ubuntu1_armhf.deb ... 339s Unpacking fontconfig-config (2.15.0-2ubuntu1) ... 339s Selecting previously unselected package gir1.2-json-1.0:armhf. 339s Preparing to unpack .../03-gir1.2-json-1.0_1.10.6+ds-1_armhf.deb ... 339s Unpacking gir1.2-json-1.0:armhf (1.10.6+ds-1) ... 339s Selecting previously unselected package libgusb2:armhf. 339s Preparing to unpack .../04-libgusb2_0.4.9-1_armhf.deb ... 339s Unpacking libgusb2:armhf (0.4.9-1) ... 339s Selecting previously unselected package gir1.2-gusb-1.0:armhf. 339s Preparing to unpack .../05-gir1.2-gusb-1.0_0.4.9-1_armhf.deb ... 339s Unpacking gir1.2-gusb-1.0:armhf (0.4.9-1) ... 339s Selecting previously unselected package libpixman-1-0:armhf. 339s Preparing to unpack .../06-libpixman-1-0_0.44.0-3_armhf.deb ... 339s Unpacking libpixman-1-0:armhf (0.44.0-3) ... 339s Selecting previously unselected package libfprint-2-tod1:armhf. 339s Preparing to unpack .../07-libfprint-2-tod1_1%3a1.94.9+tod1-1_armhf.deb ... 339s Unpacking libfprint-2-tod1:armhf (1:1.94.9+tod1-1) ... 339s Selecting previously unselected package libfprint-2-2. 339s Preparing to unpack .../08-libfprint-2-2_1%3a1.94.9+tod1-1_armhf.deb ... 339s Unpacking libfprint-2-2 (1:1.94.9+tod1-1) ... 339s Selecting previously unselected package gir1.2-fprint-2.0:armhf. 339s Preparing to unpack .../09-gir1.2-fprint-2.0_1%3a1.94.9+tod1-1_armhf.deb ... 339s Unpacking gir1.2-fprint-2.0:armhf (1:1.94.9+tod1-1) ... 339s Selecting previously unselected package gnome-desktop-testing. 339s Preparing to unpack .../10-gnome-desktop-testing_2021.1-4_armhf.deb ... 339s Unpacking gnome-desktop-testing (2021.1-4) ... 339s Selecting previously unselected package libfreetype6:armhf. 339s Preparing to unpack .../11-libfreetype6_2.13.3+dfsg-1_armhf.deb ... 339s Unpacking libfreetype6:armhf (2.13.3+dfsg-1) ... 339s Selecting previously unselected package libfontconfig1:armhf. 339s Preparing to unpack .../12-libfontconfig1_2.15.0-2ubuntu1_armhf.deb ... 339s Unpacking libfontconfig1:armhf (2.15.0-2ubuntu1) ... 339s Selecting previously unselected package libxcb-render0:armhf. 339s Preparing to unpack .../13-libxcb-render0_1.17.0-2_armhf.deb ... 339s Unpacking libxcb-render0:armhf (1.17.0-2) ... 339s Selecting previously unselected package libxcb-shm0:armhf. 339s Preparing to unpack .../14-libxcb-shm0_1.17.0-2_armhf.deb ... 339s Unpacking libxcb-shm0:armhf (1.17.0-2) ... 339s Selecting previously unselected package libxrender1:armhf. 339s Preparing to unpack .../15-libxrender1_1%3a0.9.10-1.1build1_armhf.deb ... 339s Unpacking libxrender1:armhf (1:0.9.10-1.1build1) ... 339s Selecting previously unselected package libcairo2:armhf. 339s Preparing to unpack .../16-libcairo2_1.18.2-2_armhf.deb ... 339s Unpacking libcairo2:armhf (1.18.2-2) ... 339s Selecting previously unselected package python3-cairo. 339s Preparing to unpack .../17-python3-cairo_1.26.1-2build1_armhf.deb ... 339s Unpacking python3-cairo (1.26.1-2build1) ... 339s Selecting previously unselected package libumockdev0:armhf. 339s Preparing to unpack .../18-libumockdev0_0.19.1-3_armhf.deb ... 339s Unpacking libumockdev0:armhf (0.19.1-3) ... 339s Selecting previously unselected package umockdev. 340s Preparing to unpack .../19-umockdev_0.19.1-3_armhf.deb ... 340s Unpacking umockdev (0.19.1-3) ... 340s Selecting previously unselected package libfprint-2-tests. 340s Preparing to unpack .../20-libfprint-2-tests_1%3a1.94.9+tod1-1_armhf.deb ... 340s Unpacking libfprint-2-tests (1:1.94.9+tod1-1) ... 340s Setting up gnome-desktop-testing (2021.1-4) ... 340s Setting up libpixman-1-0:armhf (0.44.0-3) ... 340s Setting up libxrender1:armhf (1:0.9.10-1.1build1) ... 340s Setting up libxcb-render0:armhf (1.17.0-2) ... 340s Setting up libgusb2:armhf (0.4.9-1) ... 340s Setting up libfprint-2-tod1:armhf (1:1.94.9+tod1-1) ... 340s Setting up libxcb-shm0:armhf (1.17.0-2) ... 340s Setting up libfreetype6:armhf (2.13.3+dfsg-1) ... 340s Setting up fonts-dejavu-mono (2.37-8) ... 340s Setting up fonts-dejavu-core (2.37-8) ... 340s Setting up libumockdev0:armhf (0.19.1-3) ... 340s Setting up gir1.2-json-1.0:armhf (1.10.6+ds-1) ... 340s Setting up libfprint-2-2 (1:1.94.9+tod1-1) ... 355s Setting up umockdev (0.19.1-3) ... 355s Setting up fontconfig-config (2.15.0-2ubuntu1) ... 355s Setting up gir1.2-gusb-1.0:armhf (0.4.9-1) ... 355s Setting up gir1.2-fprint-2.0:armhf (1:1.94.9+tod1-1) ... 355s Processing triggers for libc-bin (2.40-4ubuntu1) ... 355s Processing triggers for man-db (2.13.0-1) ... 356s Processing triggers for udev (257.2-3ubuntu1) ... 356s Processing triggers for sgml-base (1.31) ... 356s Setting up libfontconfig1:armhf (2.15.0-2ubuntu1) ... 356s Setting up libcairo2:armhf (1.18.2-2) ... 356s Setting up python3-cairo (1.26.1-2build1) ... 357s Setting up libfprint-2-tests (1:1.94.9+tod1-1) ... 357s Processing triggers for libc-bin (2.40-4ubuntu1) ... 366s autopkgtest [05:08:06]: test installed-tests: gnome-desktop-testing-runner libfprint-2 366s autopkgtest [05:08:06]: test installed-tests: [----------------------- 368s Running test: libfprint-2/driver-egismoc-0586.test 368s ** (umockdev-run:1863): DEBUG: 05:08:08.185: umockdev.vala:127: Created udev test bed /tmp/umockdev.5XVF22 368s ** (umockdev-run:1863): DEBUG: 05:08:08.186: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 368s ** (umockdev-run:1863): DEBUG: 05:08:08.188: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 368s ** (umockdev-run:1863): DEBUG: 05:08:08.193: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.5XVF22/dev/bus/usb/001/021 368s ** (umockdev-run:1863): DEBUG: 05:08:08.193: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 368s ** (umockdev-run:1863): DEBUG: 05:08:08.195: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 368s ** (umockdev-run:1863): DEBUG: 05:08:08.199: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.5XVF22/dev/bus/usb/001/001 368s ** (umockdev-run:1863): DEBUG: 05:08:08.199: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 368s ** (umockdev-run:1863): DEBUG: 05:08:08.199: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 368s (process:1867): libfprint-context-DEBUG: 05:08:08.307: Initializing FpContext (libfprint version 1.94.9+tod1) 368s (process:1867): libfprint-tod-DEBUG: 05:08:08.308: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.311: 130947305328: ../libfprint/drivers/egismoc/egismoc.c:1597 368s (process:1867): libfprint-context-DEBUG: 05:08:08.311: No driver found for USB device 1D6B:0002 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.312: egismoc_probe enter --> 368s (process:1867): libfprint-device-DEBUG: 05:08:08.313: Device reported probe completion 368s (process:1867): libfprint-device-DEBUG: 05:08:08.313: Completing action FPI_DEVICE_ACTION_PROBE in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.313: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.315: Opening device 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.315: [egismoc] DEV_INIT_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.316: [egismoc] DEV_INIT_STATES entering state 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.317: [egismoc] DEV_INIT_STATES entering state 2 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.318: [egismoc] DEV_INIT_STATES entering state 3 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.318: [egismoc] DEV_INIT_STATES entering state 4 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.319: [egismoc] DEV_INIT_STATES entering state 5 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.319: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.319: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.319: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.320: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.321: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.321: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.321: Firmware version callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.321: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.321: Device firmware version is 9050.6.2.56 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.321: [egismoc] DEV_INIT_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.321: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.321: Device reported open completion 368s (process:1867): libfprint-device-DEBUG: 05:08:08.321: Completing action FPI_DEVICE_ACTION_OPEN in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.321: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.321: List 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.321: [egismoc] LIST_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.321: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.321: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.321: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.322: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.323: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.323: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.323: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.323: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.323: Number of currently enrolled fingerprints on the device is 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.323: [egismoc] LIST_STATES entering state 1 368s (process:1867): libfprint-device-DEBUG: 05:08:08.323: Device reported listing completion 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.323: [egismoc] LIST_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.323: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.323: Completing action FPI_DEVICE_ACTION_LIST in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.323: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.323: Clear storage 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.323: [egismoc] DELETE_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.323: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.323: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.323: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.324: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.325: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.325: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.325: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.325: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.325: Number of currently enrolled fingerprints on the device is 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.325: [egismoc] DELETE_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.325: Get delete command 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.325: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.325: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.325: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.325: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.326: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.326: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.326: Delete callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.326: Response prefix valid: yes 368s (process:1867): libfprint-device-DEBUG: 05:08:08.326: Device reported deletion completion 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.326: [egismoc] DELETE_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.326: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.326: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.326: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.326: List 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.326: [egismoc] LIST_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.326: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.326: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.326: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.327: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.328: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.328: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.328: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.328: Number of currently enrolled fingerprints on the device is 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.328: [egismoc] LIST_STATES entering state 1 368s (process:1867): libfprint-device-DEBUG: 05:08:08.328: Device reported listing completion 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.328: [egismoc] LIST_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.328: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.328: Completing action FPI_DEVICE_ACTION_LIST in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.328: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 368s (process:1867): libfprint-device-DEBUG: 05:08:08.328: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.329: Enroll 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.329: [egismoc] ENROLL_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.329: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.329: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.329: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.329: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.330: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.330: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.330: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.330: Number of currently enrolled fingerprints on the device is 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.330: [egismoc] ENROLL_STATES entering state 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.330: [egismoc] ENROLL_STATES entering state 2 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.330: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.330: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.330: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.331: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.331: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.332: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.332: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.332: [egismoc] ENROLL_STATES entering state 3 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.332: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.332: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.332: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.332: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.333: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.333: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.333: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.333: [egismoc] ENROLL_STATES entering state 4 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.333: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.333: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.334: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.334: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.334: [egismoc] ENROLL_STATES entering state 5 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.334: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.334: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.334: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.334: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.335: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.335: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.335: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.335: [egismoc] ENROLL_STATES entering state 6 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.335: Get check command 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.335: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.335: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.335: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.336: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.337: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.337: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.337: Enroll check callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.337: Response suffix valid: yes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.337: [egismoc] ENROLL_STATES entering state 7 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.337: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.337: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.337: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.337: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.338: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.338: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.338: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.338: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.338: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.338: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.338: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.339: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.339: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.339: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.339: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.339: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.340: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.340: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.340: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.340: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.341: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.341: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.341: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.341: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.341: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.341: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.342: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.342: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.342: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.342: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.342: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.342: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.343: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.343: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.343: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.343: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.343: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.343: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.343: Partial capture successful. Please touch the sensor again (1/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.343: Device reported enroll progress, reported 1 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.343: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.343: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.343: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.343: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.344: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.345: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.345: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.345: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.345: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.345: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.345: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.345: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.346: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.346: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.346: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.346: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.346: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.346: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.346: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.347: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.347: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.347: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.347: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.347: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.347: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.348: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.349: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.349: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.349: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.349: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.349: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.349: Partial capture successful. Please touch the sensor again (2/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.349: Device reported enroll progress, reported 2 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.349: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.349: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.349: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.349: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.349: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.350: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.350: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.350: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.350: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.350: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.350: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.350: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.350: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.351: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.351: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.351: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.351: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.351: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.351: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.352: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.352: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.352: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.352: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.352: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.352: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.352: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.353: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.353: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.353: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.353: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.353: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.353: Partial capture successful. Please touch the sensor again (3/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.353: Device reported enroll progress, reported 3 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.353: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.353: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.353: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.353: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.353: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.354: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.354: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.354: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.354: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.354: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.354: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.354: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.355: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.355: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.355: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.355: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.355: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.355: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.356: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.356: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.356: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.356: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.356: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.356: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.356: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.357: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.357: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.357: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.357: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.357: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.357: Partial capture successful. Please touch the sensor again (4/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.357: Device reported enroll progress, reported 4 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.357: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.357: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.357: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.357: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.358: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.359: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.359: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.359: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.359: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.359: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.359: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.359: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.359: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.360: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.360: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.360: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.360: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.360: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.360: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.361: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.361: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.361: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.361: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.361: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.361: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.361: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.362: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.362: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.362: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.362: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.362: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.362: Partial capture successful. Please touch the sensor again (5/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.362: Device reported enroll progress, reported 5 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.362: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.362: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.362: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.362: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.362: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.363: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.363: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.363: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.363: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.363: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.363: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.363: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.364: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.364: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.364: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.364: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.364: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.364: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.364: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.365: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.365: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.365: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.365: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.365: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.365: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.366: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.366: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.366: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.366: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.366: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.366: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.366: Partial capture successful. Please touch the sensor again (6/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.366: Device reported enroll progress, reported 6 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.366: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.366: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.366: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.366: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.367: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.368: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.368: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.368: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.368: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.368: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.368: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.368: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.368: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.369: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.369: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.369: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.369: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.369: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.369: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.370: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.370: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.370: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.370: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.370: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.370: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.370: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.371: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.371: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.371: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.371: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.371: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.371: Partial capture successful. Please touch the sensor again (7/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.371: Device reported enroll progress, reported 7 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.371: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.371: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.371: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.371: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.371: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.372: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.372: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.372: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.372: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.372: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.372: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.372: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.373: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.373: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.373: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.373: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.373: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.373: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.374: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.374: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.374: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.374: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.374: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.374: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.374: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.375: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.375: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.375: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.375: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.375: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.375: Response suffix valid: NO 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.375: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.375: Response suffix valid: yes 368s (process:1867): libfprint-device-DEBUG: 05:08:08.375: Device reported enroll progress, reported 7 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.375: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.375: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.375: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.375: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.376: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.377: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.377: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.377: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.377: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.377: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.377: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.377: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.377: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.378: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.378: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.378: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.378: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.378: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.378: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.379: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.379: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.379: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.379: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.379: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.379: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.379: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.380: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.380: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.380: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.380: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.380: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.380: Partial capture successful. Please touch the sensor again (8/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.380: Device reported enroll progress, reported 8 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.380: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.380: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.380: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.380: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.381: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.381: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.381: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.381: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.381: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.381: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.381: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.381: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.382: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.382: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.382: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.382: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.382: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.382: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.382: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.383: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.383: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.383: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.383: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.383: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.383: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.384: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.384: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.384: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.384: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.384: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.384: Response suffix valid: NO 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.384: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.384: Response suffix valid: yes 368s (process:1867): libfprint-device-DEBUG: 05:08:08.384: Device reported enroll progress, reported 8 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.384: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.384: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.384: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.384: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.385: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.388: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.388: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.388: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.388: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.388: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.388: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.388: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.389: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.389: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.389: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.389: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.389: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.389: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.389: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.390: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.390: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.390: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.390: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.390: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.390: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.391: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.391: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.391: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.391: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.391: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.391: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.391: Partial capture successful. Please touch the sensor again (9/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.391: Device reported enroll progress, reported 9 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.392: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.392: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.392: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.392: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.392: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.393: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.393: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.393: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.393: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.393: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.393: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.393: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.393: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.394: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.394: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.394: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.394: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.394: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.394: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.395: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.395: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.395: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.395: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.395: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.395: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.395: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.396: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.396: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.396: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.396: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.396: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.396: Partial capture successful. Please touch the sensor again (10/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.396: Device reported enroll progress, reported 10 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.396: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.396: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.396: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.396: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.397: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.397: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.397: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.397: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.397: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.397: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.397: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.397: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.398: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.399: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.399: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.399: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.399: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.399: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.399: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.399: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.399: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.399: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.399: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.399: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.399: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.400: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.400: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.400: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.400: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.400: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.400: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.400: Partial capture successful. Please touch the sensor again (11/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.400: Device reported enroll progress, reported 11 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.401: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.401: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.401: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.401: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.401: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.402: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.402: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.402: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.402: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.402: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.402: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.402: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.402: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.403: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.403: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.403: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.403: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.403: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.403: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.403: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.403: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.403: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.403: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.403: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.403: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.404: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.405: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.405: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.405: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.405: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.405: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.405: Partial capture successful. Please touch the sensor again (12/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.405: Device reported enroll progress, reported 12 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.405: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.405: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.405: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.405: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.405: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.406: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.406: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.406: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.406: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.406: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.406: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.406: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.406: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.407: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.407: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.407: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.407: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.407: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.407: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.408: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.408: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.408: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.408: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.408: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.408: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.408: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.409: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.409: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.409: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.409: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.409: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.409: Partial capture successful. Please touch the sensor again (13/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.409: Device reported enroll progress, reported 13 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.409: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.409: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.409: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.409: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.409: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.410: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.410: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.410: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.410: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.410: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.410: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.410: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.410: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.411: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.411: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.411: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.411: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.411: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.411: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.412: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.412: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.412: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.412: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.412: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.412: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.412: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.413: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.413: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.413: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.413: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.413: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.413: Partial capture successful. Please touch the sensor again (14/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.413: Device reported enroll progress, reported 14 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.413: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.413: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.413: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.413: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.413: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.414: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.414: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.414: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.414: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.414: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.414: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.414: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.414: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.415: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.415: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.415: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.415: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.415: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.415: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.416: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.416: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.416: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.416: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.416: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.416: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.416: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.417: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.417: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.417: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.417: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.417: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.417: Partial capture successful. Please touch the sensor again (15/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.417: Device reported enroll progress, reported 15 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.417: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.417: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.417: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.417: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.417: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.418: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.418: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.418: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.418: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.418: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.418: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.418: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.419: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.419: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.419: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.419: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.419: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.419: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.419: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.420: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.420: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.420: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.420: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.420: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.420: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.421: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.421: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.421: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.421: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.421: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.421: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.421: Partial capture successful. Please touch the sensor again (16/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.421: Device reported enroll progress, reported 16 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.421: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.421: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.421: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.421: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.422: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.422: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.422: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.422: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.422: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.422: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.422: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.422: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.423: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.424: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.424: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.424: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.424: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.424: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.424: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.424: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.424: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.424: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.424: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.424: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.424: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.425: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.425: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.425: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.425: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.425: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.425: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.425: Partial capture successful. Please touch the sensor again (17/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.425: Device reported enroll progress, reported 17 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.426: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.426: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.426: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.426: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.426: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.427: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.427: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.427: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.427: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.427: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.427: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.427: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.427: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.428: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.428: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.428: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.428: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.428: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.428: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.428: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.428: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.428: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.428: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.428: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.429: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.429: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.430: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.430: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.430: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.430: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.430: Partial capture successful. Please touch the sensor again (18/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.430: Device reported enroll progress, reported 18 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.430: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.430: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.430: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.430: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-device-DEBUG: 05:08:08.430: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.430: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.431: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.431: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.431: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.431: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.431: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.431: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.431: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.431: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.432: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.432: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.432: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.432: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.432: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.432: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.432: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.432: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.433: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.433: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.433: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.433: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.433: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.434: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.434: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.434: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.434: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.434: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.434: Partial capture successful. Please touch the sensor again (19/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.434: Device reported enroll progress, reported 19 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.434: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.434: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.434: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.434: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.435: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.435: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.435: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.435: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.435: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.436: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.436: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.436: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.436: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.437: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.437: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.437: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.437: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.437: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.437: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.437: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.437: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.437: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.437: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.437: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.437: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.438: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.439: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.439: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.439: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.439: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.439: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.439: Partial capture successful. Please touch the sensor again (20/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.439: Device reported enroll progress, reported 20 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.439: [egismoc] ENROLL_STATES entering state 12 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.439: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.439: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.439: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.439: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.440: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.440: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.440: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.440: [egismoc] ENROLL_STATES entering state 13 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.440: New fingerprint ID: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.440: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.440: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.440: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.440: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.441: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.441: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.441: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.441: [egismoc] ENROLL_STATES entering state 14 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.441: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.441: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.441: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.442: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.443: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.443: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.443: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.443: [egismoc] ENROLL_STATES entering state 15 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.443: Enrollment was successful! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.443: Device reported enroll completion 368s (process:1867): libfprint-device-DEBUG: 05:08:08.443: Device reported finger status change: FP_FINGER_STATUS_NONE 368s (process:1867): libfprint-device-DEBUG: 05:08:08.443: Print for finger FP_FINGER_LEFT_INDEX enrolled 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.443: [egismoc] ENROLL_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.443: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.443: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.443: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.443: List 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.443: [egismoc] LIST_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.443: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.443: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.443: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.443: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.444: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.444: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.444: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.444: Device fingerprint 1: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.444: Number of currently enrolled fingerprints on the device is 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.444: [egismoc] LIST_STATES entering state 1 368s (process:1867): libfprint-device-DEBUG: 05:08:08.444: Device reported listing completion 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.444: [egismoc] LIST_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.444: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.444: Completing action FPI_DEVICE_ACTION_LIST in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.444: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-device-DEBUG: 05:08:08.444: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.444: Identify or Verify 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.444: [egismoc] IDENTIFY_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.444: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.444: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.444: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.445: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.446: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.446: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.446: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.446: Device fingerprint 1: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.446: Number of currently enrolled fingerprints on the device is 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.446: [egismoc] IDENTIFY_STATES entering state 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.446: [egismoc] IDENTIFY_STATES entering state 2 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.446: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.446: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.446: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.446: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.447: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.447: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.447: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.447: [egismoc] IDENTIFY_STATES entering state 3 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.447: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.447: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.447: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.448: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.448: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.448: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.448: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.448: [egismoc] IDENTIFY_STATES entering state 4 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.448: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.448: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.449: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.449: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.449: [egismoc] IDENTIFY_STATES entering state 5 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.449: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.449: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.449: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.450: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.450: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.450: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.450: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.450: [egismoc] IDENTIFY_STATES entering state 6 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.450: Get check command 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.450: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.450: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.450: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.451: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.452: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.452: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.452: Identify check callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.452: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.452: Identify successful for: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.452: Verifying against: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-device-DEBUG: 05:08:08.452: Device reported verify result 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.452: [egismoc] IDENTIFY_STATES entering state 7 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.452: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.452: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.452: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.452: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.453: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.453: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.453: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.453: [egismoc] IDENTIFY_STATES entering state 8 368s (process:1867): libfprint-device-DEBUG: 05:08:08.453: Device reported verify completion 368s (process:1867): libfprint-device-DEBUG: 05:08:08.453: Device reported finger status change: FP_FINGER_STATUS_NONE 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.453: [egismoc] IDENTIFY_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.453: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.453: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.453: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-device-DEBUG: 05:08:08.453: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.454: Identify or Verify 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.454: [egismoc] IDENTIFY_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.454: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.454: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.454: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.454: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.455: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.455: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.455: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.455: Device fingerprint 1: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.455: Number of currently enrolled fingerprints on the device is 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.455: [egismoc] IDENTIFY_STATES entering state 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.455: [egismoc] IDENTIFY_STATES entering state 2 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.455: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.455: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.455: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.455: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.456: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.456: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.456: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.456: [egismoc] IDENTIFY_STATES entering state 3 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.456: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.456: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.456: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.457: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.457: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.457: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.457: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.457: [egismoc] IDENTIFY_STATES entering state 4 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.457: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.457: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.458: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.458: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.458: [egismoc] IDENTIFY_STATES entering state 5 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.458: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.458: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.458: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.459: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.459: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.459: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.459: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.459: [egismoc] IDENTIFY_STATES entering state 6 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.459: Get check command 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.459: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.459: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.459: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.460: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.460: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.460: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.460: Identify check callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.460: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.460: Identify successful for: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-device-DEBUG: 05:08:08.460: Device reported identify result 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.460: [egismoc] IDENTIFY_STATES entering state 7 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.460: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.460: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.460: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.461: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.462: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.462: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.462: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.462: [egismoc] IDENTIFY_STATES entering state 8 368s (process:1867): libfprint-device-DEBUG: 05:08:08.462: Device reported identify completion 368s (process:1867): libfprint-device-DEBUG: 05:08:08.462: Device reported finger status change: FP_FINGER_STATUS_NONE 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.462: [egismoc] IDENTIFY_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.462: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.462: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.462: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-device-DEBUG: 05:08:08.462: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.462: Enroll 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.462: [egismoc] ENROLL_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.462: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.462: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.462: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.463: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.464: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.464: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.464: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.464: Device fingerprint 1: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.464: Number of currently enrolled fingerprints on the device is 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.464: [egismoc] ENROLL_STATES entering state 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.464: [egismoc] ENROLL_STATES entering state 2 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.464: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.464: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.464: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.464: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.465: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.465: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.465: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.465: [egismoc] ENROLL_STATES entering state 3 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.465: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.465: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.465: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.465: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.466: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.466: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.466: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.466: [egismoc] ENROLL_STATES entering state 4 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.466: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.466: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.467: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.467: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.467: [egismoc] ENROLL_STATES entering state 5 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.467: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.467: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.467: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.467: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.468: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.468: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.468: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.468: [egismoc] ENROLL_STATES entering state 6 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.468: Get check command 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.468: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.468: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.468: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.468: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.469: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.469: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.469: Enroll check callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.469: Response suffix valid: NO 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.469: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.469: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.469: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.469: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 368s (process:1867): libfprint-device-DEBUG: 05:08:08.469: Device reported enroll completion 368s (process:1867): libfprint-device-DEBUG: 05:08:08.469: Device reported finger status change: FP_FINGER_STATUS_NONE 368s (process:1867): libfprint-device-DEBUG: 05:08:08.469: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.469: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.469: List 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.469: [egismoc] LIST_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.469: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.469: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.469: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.470: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.470: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.470: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.470: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.470: Device fingerprint 1: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.470: Number of currently enrolled fingerprints on the device is 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.470: [egismoc] LIST_STATES entering state 1 368s (process:1867): libfprint-device-DEBUG: 05:08:08.470: Device reported listing completion 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.470: [egismoc] LIST_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.470: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.470: Completing action FPI_DEVICE_ACTION_LIST in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.470: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-device-DEBUG: 05:08:08.471: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.471: Enroll 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.471: [egismoc] ENROLL_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.471: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.471: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.471: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.471: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.472: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.472: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.472: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.472: Device fingerprint 1: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.472: Number of currently enrolled fingerprints on the device is 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.472: [egismoc] ENROLL_STATES entering state 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.472: [egismoc] ENROLL_STATES entering state 2 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.472: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.472: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.472: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.472: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.473: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.473: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.473: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.473: [egismoc] ENROLL_STATES entering state 3 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.473: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.473: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.473: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.474: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.474: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.474: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.474: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.474: [egismoc] ENROLL_STATES entering state 4 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.474: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.474: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.475: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.475: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.475: [egismoc] ENROLL_STATES entering state 5 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.475: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.475: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.475: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.475: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.476: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.476: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.476: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.476: [egismoc] ENROLL_STATES entering state 6 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.476: Get check command 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.476: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.476: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.476: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.477: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.477: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.477: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.477: Enroll check callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.477: Response suffix valid: yes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.477: [egismoc] ENROLL_STATES entering state 7 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.477: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.477: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.477: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.478: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.478: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.478: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.478: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.478: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.478: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.478: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.478: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.479: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.480: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.480: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.480: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.480: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.480: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.480: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.480: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.480: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.481: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.481: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.481: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.481: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.481: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.481: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.481: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.481: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.481: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.481: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.481: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.481: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.482: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.483: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.483: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.483: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.483: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.483: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.483: Partial capture successful. Please touch the sensor again (1/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.483: Device reported enroll progress, reported 1 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.483: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.483: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.483: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.483: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.483: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.484: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.484: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.484: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.484: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.484: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.484: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.484: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.484: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.485: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.485: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.485: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.485: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.485: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.485: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.486: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.486: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.486: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.486: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.486: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.486: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.487: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.487: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.487: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.487: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.487: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.487: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.487: Partial capture successful. Please touch the sensor again (2/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.487: Device reported enroll progress, reported 2 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.487: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.487: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.487: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.487: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.488: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.488: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.488: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.488: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.488: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.488: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.488: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.488: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.489: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.490: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.490: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.490: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.490: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.490: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.490: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.491: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.491: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.491: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.491: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.491: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.491: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.492: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.492: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.492: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.492: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.492: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.492: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.492: Partial capture successful. Please touch the sensor again (3/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.492: Device reported enroll progress, reported 3 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.492: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.492: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.492: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.492: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.493: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.494: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.494: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.494: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.494: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.494: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.494: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.494: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.495: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.495: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.495: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.495: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.495: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.495: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.495: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.496: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.496: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.496: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.496: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.496: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.496: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.496: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.497: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.497: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.497: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.497: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.497: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.497: Partial capture successful. Please touch the sensor again (4/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.497: Device reported enroll progress, reported 4 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.497: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.497: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.497: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.497: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.498: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.498: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.498: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.498: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.498: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.498: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.498: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.498: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.499: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.499: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.500: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.500: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.500: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.500: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.500: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.500: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.500: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.500: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.500: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.500: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.501: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.501: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.501: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.501: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.501: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.501: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.501: Partial capture successful. Please touch the sensor again (5/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.501: Device reported enroll progress, reported 5 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.501: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.501: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.501: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.501: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.502: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.503: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.503: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.503: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.503: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.503: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.503: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.503: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.503: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.504: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.504: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.504: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.504: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.504: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.504: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.504: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.504: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.504: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.504: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.504: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.504: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.505: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.506: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.506: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.506: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.506: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.506: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.506: Partial capture successful. Please touch the sensor again (6/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.506: Device reported enroll progress, reported 6 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.506: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.506: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.506: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.506: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.506: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.507: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.507: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.507: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.507: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.507: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.507: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.507: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.507: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.508: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.508: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.508: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.508: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.508: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.508: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.509: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.509: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.509: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.509: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.509: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.509: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.509: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.510: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.510: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.510: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.510: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.510: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.510: Partial capture successful. Please touch the sensor again (7/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.510: Device reported enroll progress, reported 7 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.510: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.510: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.510: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.510: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.510: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.511: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.511: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.511: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.511: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.511: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.511: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.511: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.511: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.512: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.512: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.512: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.512: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.512: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.512: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.513: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.513: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.513: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.513: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.513: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.513: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.513: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.514: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.514: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.514: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.514: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.514: Response suffix valid: NO 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.514: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.514: Response suffix valid: yes 368s (process:1867): libfprint-device-DEBUG: 05:08:08.514: Device reported enroll progress, reported 7 of 20 have been completed 368s listing - device should have prints 368s clear device storage 368s clear done 368s listing - device should be empty 368s enrolling 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 1, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 2, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 3, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 4, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 5, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 6, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 7, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 8, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 9, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 10, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 11, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 12, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 13, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 14, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 15, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 16, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 17, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 18, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 19, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 20, , None, None) 368s enroll done 368s listing - device should have 1 print 368s verifying 368s verify done 368s async identifying 368s indentification_done: 368s try to enroll duplicate 368s duplicate enroll attempt done 368s listing - device should still only have 1 print 368s enroll new finger 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 1, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 2, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 3, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 4, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 5, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 6, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 7, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))(process:1867): libfprint-SSM-DEBUG: 05:08:08.514: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.514: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.514: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.514: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.515: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.515: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.515: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.515: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.515: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.515: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.515: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.515: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.516: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.516: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.517: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.517: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.517: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.517: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.517: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.517: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.517: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.517: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.517: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.517: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.517: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.518: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.518: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.518: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.518: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.518: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.518: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.518: Partial capture successful. Please touch the sensor again (8/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.518: Device reported enroll progress, reported 8 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.518: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.518: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.518: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.518: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.519: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.519: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.520: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.520: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.520: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.520: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.520: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.520: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.520: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.521: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.521: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.521: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.521: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.521: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.521: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.521: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.521: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.521: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.521: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.521: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.521: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.522: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.522: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.522: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.522: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.522: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.522: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.522: Partial capture successful. Please touch the sensor again (9/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.522: Device reported enroll progress, reported 9 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.522: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.522: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.522: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.522: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.523: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.524: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.524: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.524: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.524: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.524: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.524: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.524: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.524: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.525: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.525: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.525: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.525: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.525: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.525: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.525: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.525: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.525: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.525: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.525: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.525: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.526: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.526: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.526: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.526: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.526: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.526: Response suffix valid: NO 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.526: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.526: Response suffix valid: yes 368s (process:1867): libfprint-device-DEBUG: 05:08:08.526: Device reported enroll progress, reported 9 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.527: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.527: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.527: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.527: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.527: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.528: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.528: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.528: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.528: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.528: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.528: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.528: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.528: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.529: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.529: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.529: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.529: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.529: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.529: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.529: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.529: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.529: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.529: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.529: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.529: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.530: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.531: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.531: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.531: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.531: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.531: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.531: Partial capture successful. Please touch the sensor again (10/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.531: Device reported enroll progress, reported 10 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.531: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.531: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.531: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.531: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.531: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.532: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.532: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.532: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.532: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.532: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.532: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.532: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.532: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.533: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.533: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.533: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.533: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.533: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.533: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.533: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.533: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.533: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.533: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.533: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.533: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.534: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.535: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.535: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.535: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.535: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.535: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.535: Partial capture successful. Please touch the sensor again (11/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.535: Device reported enroll progress, reported 11 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.535: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.535: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.535: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.535: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.535: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.536: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.536: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.536: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.536: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.536: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.536: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.536: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.536: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.537: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.537: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.537: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.537: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.537: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.537: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.537: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.537: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.537: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.537: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.537: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.537: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.538: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.539: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.539: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.539: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.539: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.539: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.539: Partial capture successful. Please touch the sensor again (12/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.539: Device reported enroll progress, reported 12 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.539: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.539: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.539: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.539: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.539: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.540: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.540: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.540: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.540: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.540: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.540: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.540: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.540: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.541: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.541: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.541: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.541: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.541: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.541: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.542: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.542: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.542: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.542: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.542: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.542: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.542: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.543: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.543: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.543: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.543: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.543: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.543: Partial capture successful. Please touch the sensor again (13/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.543: Device reported enroll progress, reported 13 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.543: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.543: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.543: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.543: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.543: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.544: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.544: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.544: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.544: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.544: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.544: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.544: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.545: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.545: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.545: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.545: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.545: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.545: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.545: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.546: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.546: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.546: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.546: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.546: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.546: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.546: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.547: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.547: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.547: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.547: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.547: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.547: Partial capture successful. Please touch the sensor again (14/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.547: Device reported enroll progress, reported 14 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.547: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.547: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.547: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.547: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.547: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.548: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.548: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.548: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.548: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.548: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.548: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.548: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.549: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.549: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.549: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.549: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.549: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.549: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.549: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.550: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.550: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.550: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.550: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.550: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.550: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.550: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.551: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.551: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.551: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.551: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.551: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.551: Partial capture successful. Please touch the sensor again (15/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.551: Device reported enroll progress, reported 15 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.551: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.551: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.551: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.551: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.551: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.552: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.552: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.552: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.552: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.552: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.552: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.552: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.553: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.554: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.554: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.554: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.554: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.554: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.554: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.554: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.554: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.554: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.555: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.555: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.555: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.555: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.556: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.556: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.556: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.556: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.556: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.556: Partial capture successful. Please touch the sensor again (16/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.556: Device reported enroll progress, reported 16 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.556: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.556: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.556: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.556: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.557: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.557: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.557: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.557: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.557: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.557: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.557: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.557: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.558: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.558: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.558: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.558: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.558: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.558: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.558: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.559: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.559: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.559: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.559: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.559: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.559: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.560: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.560: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.560: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.560: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.560: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.560: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.560: Partial capture successful. Please touch the sensor again (17/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.560: Device reported enroll progress, reported 17 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.560: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.560: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.560: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.560: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.561: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.561: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.561: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.561: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.561: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.561: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.561: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.561: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.562: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.563: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.563: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.563: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.563: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.563: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.563: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.563: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.563: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.563: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.563: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.563: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.564: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.564: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.564: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.564: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.564: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.564: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.564: Partial capture successful. Please touch the sensor again (18/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.564: Device reported enroll progress, reported 18 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.565: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.565: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.565: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.565: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.565: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.566: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.566: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.566: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.566: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.566: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.566: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.566: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.566: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.567: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.567: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.567: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.567: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.567: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.567: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.567: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.567: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.567: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.567: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.567: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.567: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.568: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.569: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.569: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.569: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.569: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.569: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.569: Partial capture successful. Please touch the sensor again (19/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.569: Device reported enroll progress, reported 19 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.569: [egismoc] ENROLL_STATES entering state 8 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.569: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.569: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.569: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.570: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.570: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.570: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.570: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.570: [egismoc] ENROLL_STATES entering state 9 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.570: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.570: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.570: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.571: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.571: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.571: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.571: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.571: [egismoc] ENROLL_STATES entering state 10 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.571: Wait for finger on sensor 368s (process:1867): libfprint-device-DEBUG: 05:08:08.571: Device reported finger status change: FP_FINGER_STATUS_NEEDED 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.572: Finger on sensor callback 368s (process:1867): libfprint-device-DEBUG: 05:08:08.572: Device reported finger status change: FP_FINGER_STATUS_PRESENT 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.572: [egismoc] ENROLL_STATES entering state 11 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.572: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.572: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.572: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.573: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.573: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.573: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.573: Read capture callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.573: Response prefix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.573: Response suffix valid: yes 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.573: Partial capture successful. Please touch the sensor again (20/20) 368s (process:1867): libfprint-device-DEBUG: 05:08:08.573: Device reported enroll progress, reported 20 of 20 have been completed 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.573: [egismoc] ENROLL_STATES entering state 12 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.573: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.573: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.573: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.574: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.574: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.574: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.574: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.574: [egismoc] ENROLL_STATES entering state 13 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.574: New fingerprint ID: FP1-00000000-7-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.574: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.574: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.574: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.575: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.575: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.575: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.575: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.575: [egismoc] ENROLL_STATES entering state 14 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.575: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.575: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.575: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.576: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.577: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.577: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.577: Task SSM next state callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.577: [egismoc] ENROLL_STATES entering state 15 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.577: Enrollment was successful! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.577: Device reported enroll completion 368s (process:1867): libfprint-device-DEBUG: 05:08:08.577: Device reported finger status change: FP_FINGER_STATUS_NONE 368s (process:1867): libfprint-device-DEBUG: 05:08:08.577: Print for finger FP_FINGER_RIGHT_INDEX enrolled 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.577: [egismoc] ENROLL_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.577: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.577: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.577: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.577: List 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.577: [egismoc] LIST_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.577: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.577: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.577: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.577: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.578: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.578: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.578: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.578: Device fingerprint 1: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.578: Device fingerprint 2: FP1-00000000-7-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.578: Number of currently enrolled fingerprints on the device is 2 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.578: [egismoc] LIST_STATES entering state 1 368s (process:1867): libfprint-device-DEBUG: 05:08:08.578: Device reported listing completion 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.578: [egismoc] LIST_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.578: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.578: Completing action FPI_DEVICE_ACTION_LIST in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.578: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.578: Delete 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.578: [egismoc] DELETE_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.578: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.578: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.578: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.579: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.579: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.579: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.579: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.579: Device fingerprint 1: FP1-00000000-2-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.579: Device fingerprint 2: FP1-00000000-7-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.579: Number of currently enrolled fingerprints on the device is 2 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.579: [egismoc] DELETE_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.579: Get delete command 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.579: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.579: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.579: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.579: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.580: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.580: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.580: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.580: Delete callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.580: Response prefix valid: yes 368s (process:1867): libfprint-device-DEBUG: 05:08:08.580: Device reported deletion completion 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.580: [egismoc] DELETE_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.580: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.580: Completing action FPI_DEVICE_ACTION_DELETE in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.580: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.581: List 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.581: [egismoc] LIST_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.581: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.581: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.581: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.581: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.582: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.582: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.582: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.582: Device fingerprint 1: FP1-00000000-7-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.582: Number of currently enrolled fingerprints on the device is 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.582: [egismoc] LIST_STATES entering state 1 368s (process:1867): libfprint-device-DEBUG: 05:08:08.582: Device reported listing completion 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.582: [egismoc] LIST_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.582: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.582: Completing action FPI_DEVICE_ACTION_LIST in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.582: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.582: Clear storage 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.582: [egismoc] DELETE_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.582: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.582: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.582: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.582: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.583: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.583: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.583: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.583: Device fingerprint 1: FP1-00000000-7-00000000-nobody 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.583: Number of currently enrolled fingerprints on the device is 1 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.583: [egismoc] DELETE_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.583: Get delete command 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.583: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.583: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.583: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.583: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.584: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.584: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.584: Delete callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.584: Response prefix valid: yes 368s (process:1867): libfprint-device-DEBUG: 05:08:08.584: Device reported deletion completion 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.584: [egismoc] DELETE_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.584: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.584: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.584: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.584: List 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.584: [egismoc] LIST_STATES entering state 0 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.584: Execute command and get response 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.584: Get check bytes 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.584: [egismoc] CMD_STATES entering state 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.585: [egismoc] CMD_STATES entering state 1 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.585: Command receive callback 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.585: [egismoc] CMD_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.585: List callback 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.585: Number of currently enrolled fingerprints on the device is 0 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.585: [egismoc] LIST_STATES entering state 1 368s (process:1867): libfprint-device-DEBUG: 05:08:08.585: Device reported listing completion 368s (process:1867): libfprint-SSM-DEBUG: 05:08:08.585: [egismoc] LIST_STATES completed successfully 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.585: Task SSM done 368s (process:1867): libfprint-device-DEBUG: 05:08:08.585: Completing action FPI_DEVICE_ACTION_LIST in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.585: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.585: Closing device 368s (process:1867): libfprint-egismoc-DEBUG: 05:08:08.585: Cancel 368s (process:1867): libfprint-device-DEBUG: 05:08:08.586: Device reported close completion 368s (process:1867): libfprint-device-DEBUG: 05:08:08.586: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 368s (process:1867): libfprint-device-DEBUG: 05:08:08.586: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 368s 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 8, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 9, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 10, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 11, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 12, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 13, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 14, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 15, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 16, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 17, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 18, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 19, , None, None) 368s finger status: 368s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf4a0a928 (FpiDeviceEgisMoc at 0x24e9f20)>, 20, , None, None) 368s enroll new finger done 368s listing - device should have 2 prints 368s deleting first print 368s delete done 368s listing - device should only have second print 368s clear device storage 368s clear done 368s listing - device should be empty 368s ** (umockdev-run:1863): DEBUG: 05:08:08.610: umockdev.vala:154: Removing test bed /tmp/umockdev.5XVF22 368s (umockdev-run:1863): GLib-DEBUG: 05:08:08.617: unsetenv() is not thread-safe and should not be used after threads are created 368s PASS: libfprint-2/driver-egismoc-0586.test 368s Running test: libfprint-2/driver-elanspi.test 368s ** (umockdev-run:1875): DEBUG: 05:08:08.675: umockdev.vala:127: Created udev test bed /tmp/umockdev.PY0312 368s ** (umockdev-run:1875): DEBUG: 05:08:08.675: 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 368s ** (umockdev-run:1875): DEBUG: 05:08:08.676: 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) 368s ** (umockdev-run:1875): DEBUG: 05:08:08.677: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.PY0312/dev/hidraw0: got pty /dev/pts/1 368s ** (umockdev-run:1875): DEBUG: 05:08:08.677: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.PY0312/dev/.ptymap/_dev_pts_1 368s ** (umockdev-run:1875): DEBUG: 05:08:08.677: 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 368s ** (umockdev-run:1875): DEBUG: 05:08:08.678: 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) 368s ** (umockdev-run:1875): DEBUG: 05:08:08.679: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 368s ** (umockdev-run:1875): DEBUG: 05:08:08.679: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 (subsystem i2c) 368s ** (umockdev-run:1875): DEBUG: 05:08:08.681: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 368s ** (umockdev-run:1875): DEBUG: 05:08:08.681: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 (subsystem i2c) 368s ** (umockdev-run:1875): DEBUG: 05:08:08.682: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1 368s ** (umockdev-run:1875): DEBUG: 05:08:08.682: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1 (subsystem platform) 368s ** (umockdev-run:1875): DEBUG: 05:08:08.683: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1 368s ** (umockdev-run:1875): DEBUG: 05:08:08.683: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1 (subsystem pci) 368s ** (umockdev-run:1875): DEBUG: 05:08:08.686: 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 368s ** (umockdev-run:1875): DEBUG: 05:08:08.686: 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) 368s ** (umockdev-run:1875): DEBUG: 05:08:08.687: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.PY0312/dev/spidev0.0: got pty /dev/pts/2 368s ** (umockdev-run:1875): DEBUG: 05:08:08.687: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.PY0312/dev/.ptymap/_dev_pts_2 368s ** (umockdev-run:1875): DEBUG: 05:08:08.687: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 368s ** (umockdev-run:1875): DEBUG: 05:08:08.688: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 (subsystem spi) 368s ** (umockdev-run:1875): DEBUG: 05:08:08.691: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 368s ** (umockdev-run:1875): DEBUG: 05:08:08.692: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 (subsystem spi_master) 368s ** (umockdev-run:1875): DEBUG: 05:08:08.695: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 368s ** (umockdev-run:1875): DEBUG: 05:08:08.695: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 (subsystem platform) 368s ** (umockdev-run:1875): DEBUG: 05:08:08.696: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2 368s ** (umockdev-run:1875): DEBUG: 05:08:08.696: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2 (subsystem pci) 368s (umockdev-run:1875): GLib-GIO-DEBUG: 05:08:08.699: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 368s (process:1879): libfprint-context-DEBUG: 05:08:08.847: Initializing FpContext (libfprint version 1.94.9+tod1) 368s (process:1879): libfprint-tod-DEBUG: 05:08:08.847: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 368s (process:1879): libfprint-device-DEBUG: 05:08:08.850: Device reported probe completion 368s (process:1879): libfprint-device-DEBUG: 05:08:08.850: Completing action FPI_DEVICE_ACTION_PROBE in idle! 368s (process:1879): libfprint-device-DEBUG: 05:08:08.851: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.851: 130947845517: ../libfprint/drivers/elanspi.c:1562 368s (process:1879): libfprint-image_device-DEBUG: 05:08:08.852: Image device open completed 368s (process:1879): libfprint-device-DEBUG: 05:08:08.852: Device reported open completion 368s (process:1879): libfprint-device-DEBUG: 05:08:08.852: Completing action FPI_DEVICE_ACTION_OPEN in idle! 368s (process:1879): libfprint-device-DEBUG: 05:08:08.852: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 368s (process:1879): libfprint-device-DEBUG: 05:08:08.852: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 368s (process:1879): libfprint-image_device-DEBUG: 05:08:08.852: Activating image device 368s (process:1879): libfprint-image_device-DEBUG: 05:08:08.852: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.852: [elanspi] ELANSPI_INIT_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.854: [elanspi] ELANSPI_INIT_NSTATES entering state 1 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.854: got status 81 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.854: sync hw reset 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.854: [elanspi] ELANSPI_INIT_NSTATES entering state 2 368s libfprint-Message: 05:08:08.852: Failed to read spidev block size, using 4096 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.859: [elanspi] ELANSPI_INIT_NSTATES entering state 3 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.859: sw reset ok 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.859: [elanspi] ELANSPI_INIT_NSTATES entering state 4 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.859: raw height = 96 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.860: [elanspi] ELANSPI_INIT_NSTATES entering state 5 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.860: raw width = 96 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.860: [elanspi] ELANSPI_INIT_NSTATES entering state 6 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.860: raw reg17 = 175 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.861: [elanspi] ELANSPI_INIT_NSTATES entering state 7 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.861: raw version = 09 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.861: after hardcoded lookup; 96x96, version 1 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.861: found sensor ID 6 => [eFSA96SA] (96 x 96) 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.861: [elanspi] ELANSPI_INIT_NSTATES entering state 8 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.865: [elanspi] ELANSPI_INIT_NSTATES entering state 9 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.866: [elanspi] ELANSPI_INIT_NSTATES entering state 10 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.866: [elanspi] ELANSPI_INIT_NSTATES entering state 11 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.867: [elanspi] ELANSPI_INIT_NSTATES entering state 12 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.867: [elanspi] ELANSPI_INIT_NSTATES entering state 13 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.867: [elanspi] ELANSPI_INIT_NSTATES entering state 14 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.867: [elanspi] ELANSPI_INIT_NSTATES entering state 17 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.867: got vcm mode = 2 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.868: [elanspi] ELANSPI_INIT_NSTATES entering state 18 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.868: [elanspi] ELANSPI_INIT_NSTATES entering state 19 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.868: starting calibrate 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.868: [elanspi] old calibrate entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.870: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.871: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.871: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.871: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.871: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.872: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.872: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.872: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.872: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.872: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.872: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.873: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.873: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.873: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.873: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.873: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.873: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.873: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.873: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.874: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.874: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.874: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.874: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.874: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.874: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.875: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.875: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.875: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.875: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.875: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.875: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.876: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.876: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.876: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.876: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.877: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.877: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.877: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.877: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.877: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.877: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.878: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.878: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.878: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.878: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.878: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.878: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.879: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.879: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.879: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.879: [elanspi] ELANSPI_WRTABLE_NSTATES completed successfully 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.879: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.936: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 368s (process:1879): libfprint-elanspi-DEBUG: 05:08:08.936: dac init is 0x29 368s (process:1879): libfprint-SSM-DEBUG: 05:08:08.936: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 368s (process:1879): libfprint-device-DEBUG: 05:08:08.952: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 369s (process:1879): libfprint-SSM-DEBUG: 05:08:08.994: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:08.994: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.077: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.077: calibration ok, saving bg image 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.078: [elanspi] old calibrate completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.078: [elanspi] ELANSPI_INIT_NSTATES entering state 20 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.078: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.149: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.149: [elanspi] ELANSPI_INIT_NSTATES entering state 21 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.149: [elanspi] ELANSPI_INIT_NSTATES completed successfully 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.149: 130948143303: ../libfprint/drivers/elanspi.c:1596 369s (process:1879): libfprint-image_device-DEBUG: 05:08:09.149: Image device activation completed 369s (process:1879): libfprint-image_device-DEBUG: 05:08:09.149: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 369s (process:1879): libfprint-image_device-DEBUG: 05:08:09.149: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.149: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.149: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.149: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.149: started capturer 369s (process:1879): libfprint-device-DEBUG: 05:08:09.149: Device reported finger status change: FP_FINGER_STATUS_NEEDED 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.216: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.216: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.216: stddev=933d, ip=40, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.216: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.216: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.278: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.278: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.279: stddev=829d, ip=48, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.279: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.279: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.340: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.340: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.340: stddev=1307d, ip=37, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.340: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.340: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.401: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.401: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.401: stddev=1163d, ip=38, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.401: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.401: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.464: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.464: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.464: stddev=960d, ip=43, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.464: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.464: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.523: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.523: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.524: stddev=879d, ip=41, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.524: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.524: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.580: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.580: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.581: stddev=925d, ip=44, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.581: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.581: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.643: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.643: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.643: stddev=1244d, ip=37, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.643: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.643: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.707: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.707: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.707: stddev=709d, ip=48, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.707: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.707: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.767: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.767: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.767: stddev=553d, ip=54, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.767: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.767: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.824: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.824: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.825: stddev=904d, ip=44, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.825: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.825: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.882: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.882: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.882: stddev=951d, ip=46, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.882: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.882: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.939: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.939: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 369s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.939: stddev=795d, ip=44, is_fp=0, is_empty=2 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.939: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 369s (process:1879): libfprint-SSM-DEBUG: 05:08:09.939: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:09.994: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:09.995: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:09.995: stddev=985d, ip=41, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:09.995: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:09.995: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.054: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.054: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.054: stddev=938d, ip=40, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.054: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.054: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.122: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.122: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.123: stddev=846d, ip=40, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.123: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.124: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.181: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.181: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.181: stddev=693d, ip=56, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.181: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.181: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.238: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.238: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.239: stddev=777d, ip=50, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.239: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.239: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.305: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.305: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.306: stddev=824d, ip=45, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.306: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.306: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.365: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.365: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.366: stddev=521d, ip=50, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.366: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.366: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.425: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.425: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.425: stddev=670d, ip=47, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.425: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.425: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.490: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.490: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.491: stddev=1262d, ip=39, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.491: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.491: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.552: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.552: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.552: stddev=912d, ip=42, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.552: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.552: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.614: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.614: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.615: stddev=1402d, ip=37, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.615: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.615: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.674: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.674: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.674: stddev=1530d, ip=32, is_fp=0, is_empty=2 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.674: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.674: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.736: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.736: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.736: stddev=718159d, ip=6, is_fp=1, is_empty=0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.736: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.736: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.794: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.794: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.795: stddev=400929d, ip=0, is_fp=2, is_empty=0 370s (process:1879): libfprint-device-DEBUG: 05:08:10.795: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 370s (process:1879): libfprint-image_device-DEBUG: 05:08:10.795: Image device reported finger status: on 370s (process:1879): libfprint-image_device-DEBUG: 05:08:10.795: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.795: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.795: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.860: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.860: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.860: stddev=346514d, ip=0, is_fp=1, is_empty=0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.861: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.861: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.921: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.921: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.922: stddev=324160d, ip=0, is_fp=1, is_empty=0 370s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.923: diff = 107344 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.923: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 370s (process:1879): libfprint-SSM-DEBUG: 05:08:10.923: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:10.983: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:10.983: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.983: stddev=339430d, ip=0, is_fp=1, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:10.984: diff = 246471 371s (process:1879): libfprint-SSM-DEBUG: 05:08:10.984: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:10.984: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.043: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.043: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.044: stddev=334711d, ip=0, is_fp=1, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.044: diff = 73010 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.045: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.045: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.107: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.107: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.108: stddev=317574d, ip=0, is_fp=1, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.108: diff = 58831 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.108: ignoring b.c. difference is too small 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.108: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.108: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.165: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.165: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.165: stddev=285577d, ip=0, is_fp=1, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.166: diff = 241923 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.166: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.166: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.219: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.219: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.220: stddev=417772d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.221: diff = 254823 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.221: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.221: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.274: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.274: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.275: stddev=541148d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.275: diff = 290922 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.275: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.275: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.327: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.327: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.328: stddev=580192d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.329: diff = 332283 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.329: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.329: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.382: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.382: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.382: stddev=484527d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.383: diff = 325141 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.383: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.383: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.437: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.437: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.437: stddev=482100d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.438: diff = 337412 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.438: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.438: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.490: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.490: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.490: stddev=558238d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.491: diff = 342841 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.491: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.491: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.545: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.545: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.545: stddev=572990d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.546: diff = 352690 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.546: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.546: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.603: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.603: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.603: stddev=575411d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.604: diff = 365537 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.604: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.604: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.658: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.658: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.658: stddev=578482d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.659: diff = 342041 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.659: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.659: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.713: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.713: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.713: stddev=572686d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.714: diff = 421037 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.714: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.714: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.767: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.767: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.768: stddev=465498d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.768: diff = 404640 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.769: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.769: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.827: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.827: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.827: stddev=410135d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.828: diff = 347658 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.828: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.828: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.881: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.881: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.881: stddev=493239d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.882: diff = 344237 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.882: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.882: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.934: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.934: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.935: stddev=553028d, ip=0, is_fp=2, is_empty=0 371s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.935: diff = 419597 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.935: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 371s (process:1879): libfprint-SSM-DEBUG: 05:08:11.935: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 372s (process:1879): libfprint-SSM-DEBUG: 05:08:11.989: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 372s (process:1879): libfprint-SSM-DEBUG: 05:08:11.989: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 372s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.989: stddev=574502d, ip=0, is_fp=2, is_empty=0 372s (process:1879): libfprint-elanspi-DEBUG: 05:08:11.990: diff = 408934 372s (process:1879): libfprint-SSM-DEBUG: 05:08:11.990: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 372s (process:1879): libfprint-SSM-DEBUG: 05:08:11.990: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.043: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.043: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 372s (process:1879): libfprint-elanspi-DEBUG: 05:08:12.043: stddev=645815d, ip=0, is_fp=2, is_empty=0 372s (process:1879): libfprint-elanspi-DEBUG: 05:08:12.044: diff = 409198 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.044: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.044: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.098: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.098: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 372s (process:1879): libfprint-elanspi-DEBUG: 05:08:12.099: stddev=677451d, ip=0, is_fp=2, is_empty=0 372s (process:1879): libfprint-elanspi-DEBUG: 05:08:12.100: diff = 429666 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.100: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.100: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.153: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.154: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 372s (process:1879): libfprint-elanspi-DEBUG: 05:08:12.154: stddev=634407d, ip=0, is_fp=2, is_empty=0 372s (process:1879): libfprint-elanspi-DEBUG: 05:08:12.154: have enough frames, exiting now 372s (process:1879): libfprint-assembling-DEBUG: 05:08:12.344: calc delta completed in 0.190174 secs 372s (process:1879): libfprint-assembling-DEBUG: 05:08:12.535: calc delta completed in 0.190624 secs 372s (process:1879): libfprint-assembling-DEBUG: 05:08:12.535: errors: 86516 rev: 170625 372s (process:1879): libfprint-assembling-DEBUG: 05:08:12.725: calc delta completed in 0.190209 secs 372s (process:1879): libfprint-assembling-DEBUG: 05:08:12.725: height is 246 372s (process:1879): libfprint-image_device-DEBUG: 05:08:12.727: Image device captured an image 372s (process:1879): libfprint-image_device-DEBUG: 05:08:12.728: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 372s (process:1879): libfprint-device-DEBUG: 05:08:12.728: Device reported finger status change: FP_FINGER_STATUS_PRESENT 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.728: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.728: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 372s (process:1879): libfprint-image-DEBUG: 05:08:12.784: Minutiae scan completed in 0.056036 secs 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.794: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.794: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 372s (process:1879): libfprint-elanspi-DEBUG: 05:08:12.794: stddev=593525d, ip=0, is_fp=2, is_empty=0 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.794: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.794: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.857: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.857: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 372s (process:1879): libfprint-elanspi-DEBUG: 05:08:12.858: stddev=610651d, ip=0, is_fp=2, is_empty=0 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.858: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.858: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.921: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.921: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 372s (process:1879): libfprint-elanspi-DEBUG: 05:08:12.922: stddev=505673d, ip=0, is_fp=2, is_empty=0 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.922: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 372s (process:1879): libfprint-SSM-DEBUG: 05:08:12.922: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 372s Executing: libfprint-2/driver-elanspi.test 373s (process:1879): libfprint-SSM-DEBUG: 05:08:12.988: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:12.988: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:12.988: stddev=537580d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:12.988: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:12.988: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.057: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.057: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.057: stddev=520750d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.057: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.057: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.131: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.131: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.131: stddev=468008d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.131: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.131: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.207: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.207: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.208: stddev=477058d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.208: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.208: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.274: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.274: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.274: stddev=460178d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.274: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.274: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.345: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.345: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.346: stddev=538508d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.346: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.346: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.406: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.406: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.406: stddev=661673d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.407: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.407: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.465: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.465: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.465: stddev=764706d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.465: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.465: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.522: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.523: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.523: stddev=806415d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.523: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.523: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.583: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.583: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.583: stddev=806649d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.583: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.583: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.645: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.645: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.646: stddev=822567d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.646: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.646: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.703: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.703: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.704: stddev=1017068d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.704: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.704: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.763: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.763: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.763: stddev=1004196d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.763: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.763: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.821: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.821: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.821: stddev=963655d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.821: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.821: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.880: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.880: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.880: stddev=880521d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.880: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.880: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.938: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.938: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 373s (process:1879): libfprint-elanspi-DEBUG: 05:08:13.938: stddev=1135372d, ip=0, is_fp=2, is_empty=0 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.938: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 373s (process:1879): libfprint-SSM-DEBUG: 05:08:13.938: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 374s (process:1879): libfprint-SSM-DEBUG: 05:08:14.000: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 374s (process:1879): libfprint-SSM-DEBUG: 05:08:14.000: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 374s (process:1879): libfprint-elanspi-DEBUG: 05:08:14.000: stddev=1093450d, ip=3, is_fp=1, is_empty=0 374s (process:1879): libfprint-SSM-DEBUG: 05:08:14.000: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 374s (process:1879): libfprint-SSM-DEBUG: 05:08:14.000: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 374s (process:1879): libfprint-SSM-DEBUG: 05:08:14.061: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 374s (process:1879): libfprint-SSM-DEBUG: 05:08:14.061: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 374s (process:1879): libfprint-elanspi-DEBUG: 05:08:14.061: stddev=41090d, ip=8, is_fp=0, is_empty=2 374s (process:1879): libfprint-SSM-DEBUG: 05:08:14.061: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 374s (process:1879): libfprint-SSM-DEBUG: 05:08:14.061: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 374s (process:1879): libfprint-SSM-DEBUG: 05:08:14.123: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 374s (process:1879): libfprint-SSM-DEBUG: 05:08:14.123: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 374s (process:1879): libfprint-elanspi-DEBUG: 05:08:14.123: stddev=6836d, ip=13, is_fp=0, is_empty=2 374s (process:1879): libfprint-device-DEBUG: 05:08:14.123: Device reported finger status change: FP_FINGER_STATUS_NONE 374s (process:1879): libfprint-image_device-DEBUG: 05:08:14.123: Image device reported finger status: off 374s (process:1879): libfprint-image_device-DEBUG: 05:08:14.123: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 374s (process:1879): libfprint-image_device-DEBUG: 05:08:14.123: Deactivating image device 374s (process:1879): libfprint-image_device-DEBUG: 05:08:14.123: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 374s (process:1879): libfprint-image_device-DEBUG: 05:08:14.123: Image device deactivation completed 374s (process:1879): libfprint-image_device-DEBUG: 05:08:14.123: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 374s (process:1879): libfprint-device-DEBUG: 05:08:14.123: Device reported capture completion 374s (process:1879): libfprint-SSM-DEBUG: 05:08:14.123: [elanspi] ELANSPI_FPCAPT_NSTATES completed successfully 374s (process:1879): libfprint-device-DEBUG: 05:08:14.123: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 374s (process:1879): libfprint-device-DEBUG: 05:08:14.123: Updated temperature model after 5.17 seconds, ratio 0.27 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1879): libfprint-image_device-DEBUG: 05:08:14.123: Image device close completed 374s (process:1879): libfprint-device-DEBUG: 05:08:14.123: Device reported close completion 374s (process:1879): libfprint-device-DEBUG: 05:08:14.123: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 374s (process:1879): libfprint-device-DEBUG: 05:08:14.123: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s ** (umockdev-run:1875): DEBUG: 05:08:14.391: umockdev.vala:154: Removing test bed /tmp/umockdev.PY0312 374s (umockdev-run:1875): GLib-DEBUG: 05:08:14.403: unsetenv() is not thread-safe and should not be used after threads are created 374s Comparing PNGs /tmp/libfprint-umockdev-test-4trgamt8/capture.png and /usr/share/installed-tests/libfprint-2/elanspi/capture.png 374s PASS: libfprint-2/driver-elanspi.test 374s Running test: libfprint-2/driver-egismoc-0587.test 374s ** (umockdev-run:1889): DEBUG: 05:08:14.526: umockdev.vala:127: Created udev test bed /tmp/umockdev.QPL112 374s ** (umockdev-run:1889): DEBUG: 05:08:14.526: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 374s ** (umockdev-run:1889): DEBUG: 05:08:14.529: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 374s ** (umockdev-run:1889): DEBUG: 05:08:14.534: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.QPL112/dev/bus/usb/003/009 374s ** (umockdev-run:1889): DEBUG: 05:08:14.534: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 374s ** (umockdev-run:1889): DEBUG: 05:08:14.536: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 374s ** (umockdev-run:1889): DEBUG: 05:08:14.540: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.QPL112/dev/bus/usb/003/001 374s ** (umockdev-run:1889): DEBUG: 05:08:14.540: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 374s ** (umockdev-run:1889): DEBUG: 05:08:14.540: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 374s (process:1893): libfprint-context-DEBUG: 05:08:14.653: Initializing FpContext (libfprint version 1.94.9+tod1) 374s (process:1893): libfprint-tod-DEBUG: 05:08:14.653: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.656: 130953650120: ../libfprint/drivers/egismoc/egismoc.c:1597 374s (process:1893): libfprint-context-DEBUG: 05:08:14.656: No driver found for USB device 1D6B:0002 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.657: egismoc_probe enter --> 374s (process:1893): libfprint-device-DEBUG: 05:08:14.658: Device reported probe completion 374s (process:1893): libfprint-device-DEBUG: 05:08:14.659: Completing action FPI_DEVICE_ACTION_PROBE in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.659: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.660: Opening device 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.661: [egismoc] DEV_INIT_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.661: [egismoc] DEV_INIT_STATES entering state 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.662: [egismoc] DEV_INIT_STATES entering state 2 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.663: [egismoc] DEV_INIT_STATES entering state 3 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.663: [egismoc] DEV_INIT_STATES entering state 4 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.664: [egismoc] DEV_INIT_STATES entering state 5 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.664: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.664: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.664: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.664: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.665: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.665: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.665: Firmware version callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.665: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.665: Device firmware version is 9050.6.4.67 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.665: [egismoc] DEV_INIT_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.665: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.665: Device reported open completion 374s (process:1893): libfprint-device-DEBUG: 05:08:14.665: Completing action FPI_DEVICE_ACTION_OPEN in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.665: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.666: List 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.666: [egismoc] LIST_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.666: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.666: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.666: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.666: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.667: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.667: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.667: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.667: Device fingerprint 1: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.667: Number of currently enrolled fingerprints on the device is 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.667: [egismoc] LIST_STATES entering state 1 374s (process:1893): libfprint-device-DEBUG: 05:08:14.667: Device reported listing completion 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.667: [egismoc] LIST_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.667: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.667: Completing action FPI_DEVICE_ACTION_LIST in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.667: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.667: Clear storage 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.667: [egismoc] DELETE_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.667: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.667: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.667: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.668: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.668: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.668: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.668: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.668: Device fingerprint 1: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.668: Number of currently enrolled fingerprints on the device is 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.668: [egismoc] DELETE_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.668: Get delete command 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.668: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.668: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.668: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.669: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.670: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.670: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.670: Delete callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.670: Response prefix valid: yes 374s (process:1893): libfprint-device-DEBUG: 05:08:14.670: Device reported deletion completion 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.670: [egismoc] DELETE_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.670: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.670: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.670: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.670: List 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.670: [egismoc] LIST_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.670: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.670: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.670: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.670: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.671: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.671: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.671: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.671: Number of currently enrolled fingerprints on the device is 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.671: [egismoc] LIST_STATES entering state 1 374s (process:1893): libfprint-device-DEBUG: 05:08:14.671: Device reported listing completion 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.671: [egismoc] LIST_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.671: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.671: Completing action FPI_DEVICE_ACTION_LIST in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.671: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1893): libfprint-device-DEBUG: 05:08:14.672: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.672: Enroll 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.672: [egismoc] ENROLL_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.672: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.672: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.672: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.672: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.673: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.673: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.673: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.673: Number of currently enrolled fingerprints on the device is 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.673: [egismoc] ENROLL_STATES entering state 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.673: [egismoc] ENROLL_STATES entering state 2 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.673: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.673: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.673: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.674: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.674: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.674: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.674: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.674: [egismoc] ENROLL_STATES entering state 3 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.674: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.674: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.674: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.675: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.676: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.676: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.676: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.676: [egismoc] ENROLL_STATES entering state 4 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.676: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.676: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.676: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.676: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.676: [egismoc] ENROLL_STATES entering state 5 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.676: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.676: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.676: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.677: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.678: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.678: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.678: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.678: [egismoc] ENROLL_STATES entering state 6 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.678: Get check command 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.678: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.678: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.678: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.678: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.679: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.679: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.679: Enroll check callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.679: Response suffix valid: yes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.679: [egismoc] ENROLL_STATES entering state 7 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.679: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.679: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.679: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.679: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.680: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.680: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.680: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.680: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.680: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.680: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.680: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.681: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.682: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.682: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.682: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.682: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.682: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.682: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.682: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.682: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.683: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.683: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.683: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.683: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.683: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.683: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.683: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.683: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.683: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.683: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.683: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.683: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.684: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.685: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.685: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.685: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.685: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.685: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.685: Partial capture successful. Please touch the sensor again (1/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.685: Device reported enroll progress, reported 1 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.685: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.685: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.685: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.685: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.686: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.686: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.686: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.686: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.686: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.686: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.686: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.686: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.687: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.688: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.688: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.688: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.688: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.688: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.688: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.688: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.688: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.688: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.688: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.688: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.688: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.689: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.690: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.690: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.690: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.690: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.690: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.690: Partial capture successful. Please touch the sensor again (2/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.690: Device reported enroll progress, reported 2 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.690: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.690: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.690: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.690: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.690: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.691: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.691: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.691: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.691: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.691: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.691: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.691: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.691: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.692: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.692: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.692: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.692: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.692: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.692: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.692: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.692: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.692: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.692: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.692: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.692: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.693: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.693: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.693: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.693: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.693: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.693: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.693: Partial capture successful. Please touch the sensor again (3/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.693: Device reported enroll progress, reported 3 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.694: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.694: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.694: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.694: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.694: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.695: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.695: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.695: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.695: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.695: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.695: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.695: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.695: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.696: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.696: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.696: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.696: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.696: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.696: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.696: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.696: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.696: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.696: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.696: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.696: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.697: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.697: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.697: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.697: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.697: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.697: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.697: Partial capture successful. Please touch the sensor again (4/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.697: Device reported enroll progress, reported 4 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.697: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.697: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.697: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.697: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.698: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.698: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.699: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.699: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.699: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.699: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.699: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.699: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.699: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.700: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.700: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.700: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.700: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.700: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.700: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.700: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.700: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.700: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.700: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.700: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.700: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.701: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.701: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.701: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.701: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.701: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.701: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.701: Partial capture successful. Please touch the sensor again (5/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.701: Device reported enroll progress, reported 5 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.702: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.702: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.702: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.702: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.702: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.703: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.703: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.703: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.703: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.703: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.703: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.703: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.703: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.704: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.704: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.704: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.704: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.704: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.704: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.704: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.704: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.704: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.704: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.704: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.704: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.705: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.705: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.705: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.705: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.705: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.705: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.705: Partial capture successful. Please touch the sensor again (6/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.705: Device reported enroll progress, reported 6 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.705: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.705: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.705: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.705: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.706: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.707: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.707: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.707: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.707: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.707: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.707: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.707: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.707: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.708: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.708: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.708: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.708: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.708: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.708: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.708: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.708: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.708: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.708: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.708: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.708: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.709: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.710: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.710: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.710: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.710: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.710: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.710: Partial capture successful. Please touch the sensor again (7/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.710: Device reported enroll progress, reported 7 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.710: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.710: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.710: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.710: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.710: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.711: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.711: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.711: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.711: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.711: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.711: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.711: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.711: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.712: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.712: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.712: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.712: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.712: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.713: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.713: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.713: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.713: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.713: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.713: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.713: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.714: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.714: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.714: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.714: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.714: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.714: Partial capture successful. Please touch the sensor again (8/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.714: Device reported enroll progress, reported 8 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.714: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.714: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.714: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.714: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.714: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.715: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.715: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.715: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.715: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.715: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.715: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.715: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.715: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.716: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.716: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.716: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.716: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.716: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.717: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.717: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.717: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.717: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.717: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.717: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.717: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.718: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.718: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.718: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.718: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.718: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.718: Partial capture successful. Please touch the sensor again (9/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.718: Device reported enroll progress, reported 9 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.718: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.718: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.718: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.718: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.718: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.719: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.719: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.719: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.719: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.719: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.719: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.719: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.719: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.720: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.720: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.720: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.720: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.720: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.720: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.720: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.720: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.720: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.720: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.720: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.721: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.721: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.721: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.721: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.721: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.721: Response suffix valid: NO 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.721: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.721: Response suffix valid: yes 374s (process:1893): libfprint-device-DEBUG: 05:08:14.721: Device reported enroll progress, reported 9 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.721: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.722: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.722: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.722: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.722: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.723: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.723: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.723: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.723: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.723: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.723: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.723: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.723: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.724: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.724: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.724: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.724: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.724: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.724: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.724: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.724: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.724: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.724: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.724: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.725: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.726: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.726: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.726: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.726: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.726: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.726: Partial capture successful. Please touch the sensor again (10/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.726: Device reported enroll progress, reported 10 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.726: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.726: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.726: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.726: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.726: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.727: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.727: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.727: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.727: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.727: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.727: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.727: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.727: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.728: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.728: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.728: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.728: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.728: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.729: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.729: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.729: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.729: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.729: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.729: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.729: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.730: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.730: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.730: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.730: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.730: Response suffix valid: NO 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.730: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.730: Response suffix valid: yes 374s (process:1893): libfprint-device-DEBUG: 05:08:14.730: Device reported enroll progress, reported 10 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.730: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.730: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.730: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.730: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.730: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.731: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.731: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.731: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.731: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.731: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.731: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.731: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.732: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.732: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.732: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.732: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.732: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.732: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.732: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.733: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.733: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.733: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.733: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.733: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.733: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.733: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.734: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.734: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.734: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.734: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.734: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.734: Partial capture successful. Please touch the sensor again (11/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.734: Device reported enroll progress, reported 11 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.734: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.734: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.734: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.734: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.734: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.735: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.735: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.735: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.735: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.735: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.735: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.735: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.736: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.736: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.736: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.736: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.736: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.736: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.736: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.737: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.737: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.737: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.737: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.737: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.737: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.737: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.738: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.738: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.738: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.738: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.738: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.738: Partial capture successful. Please touch the sensor again (12/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.738: Device reported enroll progress, reported 12 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.738: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.738: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.738: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.738: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.738: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.739: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.739: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.739: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.739: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.739: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.739: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.739: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.740: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.740: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.740: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.740: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.740: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.740: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.740: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.741: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.741: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.741: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.741: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.741: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.741: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.741: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.742: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.742: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.742: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.742: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.742: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.742: Partial capture successful. Please touch the sensor again (13/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.742: Device reported enroll progress, reported 13 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.742: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.742: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.742: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.742: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.743: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.743: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.743: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.743: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.743: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.743: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.743: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.743: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.744: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.744: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.744: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.744: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.744: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.744: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.744: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.745: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.745: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.745: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.745: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.745: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.745: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.745: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.746: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.746: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.746: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.746: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.746: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.746: Partial capture successful. Please touch the sensor again (14/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.746: Device reported enroll progress, reported 14 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.746: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.746: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.746: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.746: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.747: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.747: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.747: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.747: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.747: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.747: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.747: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.747: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.748: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.748: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.748: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.748: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.748: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.748: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.748: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.749: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.749: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.749: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.749: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.749: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.749: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.749: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.750: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.750: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.750: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.750: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.750: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.750: Partial capture successful. Please touch the sensor again (15/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.750: Device reported enroll progress, reported 15 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.750: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.750: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.750: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.750: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.751: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.751: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.751: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.751: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.751: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.751: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.751: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.751: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.752: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.752: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.752: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.752: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.752: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.752: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.752: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.753: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.753: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.753: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.753: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.753: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.753: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.754: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.754: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.754: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.754: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.754: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.754: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.754: Partial capture successful. Please touch the sensor again (16/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.754: Device reported enroll progress, reported 16 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.754: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.754: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.754: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.754: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.755: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.756: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.756: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.756: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.756: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.756: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.756: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.756: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.756: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.757: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.757: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.757: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.757: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.757: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.757: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.757: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.757: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.757: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.757: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.757: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.757: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.758: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.759: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.759: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.759: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.759: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.759: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.759: Partial capture successful. Please touch the sensor again (17/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.759: Device reported enroll progress, reported 17 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.759: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.759: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.759: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.759: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.759: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.760: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.760: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.760: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.760: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.760: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.760: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.760: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.760: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.761: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.761: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.761: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.761: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.761: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.761: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.762: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.762: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.762: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.762: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.762: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.762: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.762: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.763: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.763: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.763: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.763: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.763: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.763: Partial capture successful. Please touch the sensor again (18/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.763: Device reported enroll progress, reported 18 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.763: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.763: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.763: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.763: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.763: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.764: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.764: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.764: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.764: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.764: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.764: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.764: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.765: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.765: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.765: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.765: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.765: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.765: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.766: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.766: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.766: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.766: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.766: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.766: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.766: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.767: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.767: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.767: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.767: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.767: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.767: Partial capture successful. Please touch the sensor again (19/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.767: Device reported enroll progress, reported 19 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.767: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.767: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.767: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.767: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.768: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.768: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.768: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.768: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.768: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.768: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.768: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.768: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.769: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.769: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.769: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.769: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.769: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.769: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.769: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.770: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.770: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.770: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.770: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.770: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.770: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.770: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.771: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.771: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.771: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.771: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.771: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.771: Partial capture successful. Please touch the sensor again (20/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.771: Device reported enroll progress, reported 20 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.771: [egismoc] ENROLL_STATES entering state 12 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.771: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.771: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.771: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.772: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-device-DEBUG: 05:08:14.772: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.772: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.772: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.772: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.772: [egismoc] ENROLL_STATES entering state 13 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.772: New fingerprint ID: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.772: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.772: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.772: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.773: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.773: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.773: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.773: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.773: [egismoc] ENROLL_STATES entering state 14 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.773: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.773: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.773: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.774: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.775: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.775: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.775: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.775: [egismoc] ENROLL_STATES entering state 15 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.775: Enrollment was successful! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.775: Device reported enroll completion 374s (process:1893): libfprint-device-DEBUG: 05:08:14.775: Device reported finger status change: FP_FINGER_STATUS_NONE 374s (process:1893): libfprint-device-DEBUG: 05:08:14.775: Print for finger FP_FINGER_LEFT_INDEX enrolled 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.775: [egismoc] ENROLL_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.775: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.775: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.775: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.775: List 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.775: [egismoc] LIST_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.775: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.775: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.775: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.775: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.776: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.776: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.776: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.776: Device fingerprint 1: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.776: Number of currently enrolled fingerprints on the device is 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.776: [egismoc] LIST_STATES entering state 1 374s (process:1893): libfprint-device-DEBUG: 05:08:14.776: Device reported listing completion 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.776: [egismoc] LIST_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.776: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.776: Completing action FPI_DEVICE_ACTION_LIST in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.776: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-device-DEBUG: 05:08:14.776: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.776: Identify or Verify 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.776: [egismoc] IDENTIFY_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.776: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.776: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.776: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.777: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.777: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.777: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.777: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.777: Device fingerprint 1: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.777: Number of currently enrolled fingerprints on the device is 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.778: [egismoc] IDENTIFY_STATES entering state 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.778: [egismoc] IDENTIFY_STATES entering state 2 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.778: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.778: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.778: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.778: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.779: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.779: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.779: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.779: [egismoc] IDENTIFY_STATES entering state 3 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.779: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.779: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.779: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.779: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.780: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.780: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.780: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.780: [egismoc] IDENTIFY_STATES entering state 4 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.780: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.780: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.780: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.780: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.780: [egismoc] IDENTIFY_STATES entering state 5 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.781: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.781: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.781: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.781: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.782: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.782: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.782: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.782: [egismoc] IDENTIFY_STATES entering state 6 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.782: Get check command 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.782: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.782: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.782: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.782: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.783: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.783: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.783: Identify check callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.783: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.783: Identify successful for: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.783: Verifying against: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-device-DEBUG: 05:08:14.783: Device reported verify result 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.783: [egismoc] IDENTIFY_STATES entering state 7 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.783: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.783: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.783: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.783: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.784: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.784: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.784: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.784: [egismoc] IDENTIFY_STATES entering state 8 374s (process:1893): libfprint-device-DEBUG: 05:08:14.784: Device reported verify completion 374s (process:1893): libfprint-device-DEBUG: 05:08:14.784: Device reported finger status change: FP_FINGER_STATUS_NONE 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.784: [egismoc] IDENTIFY_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.784: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.784: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.784: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-device-DEBUG: 05:08:14.785: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.785: Identify or Verify 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.785: [egismoc] IDENTIFY_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.785: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.785: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.785: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.785: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.786: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.786: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.786: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.786: Device fingerprint 1: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.786: Number of currently enrolled fingerprints on the device is 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.786: [egismoc] IDENTIFY_STATES entering state 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.786: [egismoc] IDENTIFY_STATES entering state 2 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.786: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.786: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.786: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.786: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.787: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.787: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.787: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.787: [egismoc] IDENTIFY_STATES entering state 3 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.787: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.787: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.787: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.788: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.788: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.788: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.788: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.788: [egismoc] IDENTIFY_STATES entering state 4 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.788: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.788: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.789: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.789: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.789: [egismoc] IDENTIFY_STATES entering state 5 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.789: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.789: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.789: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.789: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.790: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.790: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.790: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.790: [egismoc] IDENTIFY_STATES entering state 6 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.790: Get check command 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.790: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.790: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.790: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.790: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.791: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.791: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.791: Identify check callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.791: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.791: Identify successful for: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-device-DEBUG: 05:08:14.791: Device reported identify result 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.791: [egismoc] IDENTIFY_STATES entering state 7 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.791: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.791: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.791: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.792: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.792: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.792: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.792: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.792: [egismoc] IDENTIFY_STATES entering state 8 374s (process:1893): libfprint-device-DEBUG: 05:08:14.792: Device reported identify completion 374s (process:1893): libfprint-device-DEBUG: 05:08:14.792: Device reported finger status change: FP_FINGER_STATUS_NONE 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.792: [egismoc] IDENTIFY_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.792: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.792: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.792: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-device-DEBUG: 05:08:14.793: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.793: Enroll 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.793: [egismoc] ENROLL_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.793: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.793: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.793: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.794: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.794: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.794: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.794: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.794: Device fingerprint 1: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.794: Number of currently enrolled fingerprints on the device is 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.794: [egismoc] ENROLL_STATES entering state 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.794: [egismoc] ENROLL_STATES entering state 2 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.794: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.794: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.794: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.795: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.795: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.795: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.795: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.795: [egismoc] ENROLL_STATES entering state 3 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.795: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.795: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.795: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.796: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.797: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.797: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.797: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.797: [egismoc] ENROLL_STATES entering state 4 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.797: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.797: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.797: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.797: [egismoc] ENROLL_STATES entering state 5 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.797: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.797: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.797: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.798: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.798: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.798: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.798: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.798: [egismoc] ENROLL_STATES entering state 6 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.798: Get check command 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.798: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.798: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.798: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.799: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.799: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.799: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.799: Enroll check callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.799: Response suffix valid: NO 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.799: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.799: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.799: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.799: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 374s (process:1893): libfprint-device-DEBUG: 05:08:14.799: Device reported enroll completion 374s (process:1893): libfprint-device-DEBUG: 05:08:14.799: Device reported finger status change: FP_FINGER_STATUS_NONE 374s (process:1893): libfprint-device-DEBUG: 05:08:14.799: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.799: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.800: List 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.800: [egismoc] LIST_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.800: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.800: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.800: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.800: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.801: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.801: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.801: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.801: Device fingerprint 1: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.801: Number of currently enrolled fingerprints on the device is 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.801: [egismoc] LIST_STATES entering state 1 374s (process:1893): libfprint-device-DEBUG: 05:08:14.801: Device reported listing completion 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.801: [egismoc] LIST_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.801: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.801: Completing action FPI_DEVICE_ACTION_LIST in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.801: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-device-DEBUG: 05:08:14.801: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.801: Enroll 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.801: [egismoc] ENROLL_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.801: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.801: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.801: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.802: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.802: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.802: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.802: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.802: Device fingerprint 1: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.802: Number of currently enrolled fingerprints on the device is 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.802: [egismoc] ENROLL_STATES entering state 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.802: [egismoc] ENROLL_STATES entering state 2 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.802: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.802: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.802: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.803: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.803: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.803: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.803: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.803: [egismoc] ENROLL_STATES entering state 3 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.803: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.803: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.803: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.804: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.804: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.804: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.804: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.804: [egismoc] ENROLL_STATES entering state 4 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.804: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.804: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.806: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.806: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.806: [egismoc] ENROLL_STATES entering state 5 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.806: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.806: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.806: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.807: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.808: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.808: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.808: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.808: [egismoc] ENROLL_STATES entering state 6 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.808: Get check command 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.808: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.808: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.808: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.809: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.809: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.809: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.809: Enroll check callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.809: Response suffix valid: yes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.809: [egismoc] ENROLL_STATES entering state 7 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.809: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.809: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.809: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.810: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.810: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.810: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.810: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.810: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.810: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.810: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.810: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.811: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.812: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.812: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.812: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.812: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.812: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.812: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.812: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.812: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.813: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.813: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.813: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.813: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.813: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.813: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.813: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.813: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.813: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.813: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.813: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.814: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.814: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.814: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.815: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.815: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.815: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.815: Partial capture successful. Please touch the sensor again (1/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.815: Device reported enroll progress, reported 1 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.815: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.815: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.815: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.815: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.815: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.816: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.816: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.816: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.816: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.816: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.816: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.816: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.816: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.817: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.817: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.817: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.817: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.817: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.817: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.818: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.818: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.818: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.818: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.818: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.818: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.818: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.819: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.819: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.819: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.819: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.819: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.819: Partial capture successful. Please touch the sensor again (2/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.819: Device reported enroll progress, reported 2 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.819: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.819: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.819: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.819: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.819: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.820: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.820: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.820: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.820: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.820: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.820: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.820: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.821: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.821: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.821: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.821: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.821: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.821: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.821: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.822: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.822: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.822: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.822: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.822: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.822: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.822: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.823: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.823: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.823: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.823: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.823: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.823: Partial capture successful. Please touch the sensor again (3/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.823: Device reported enroll progress, reported 3 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.823: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.823: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.823: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.823: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.823: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.824: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.824: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.824: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.824: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.824: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.824: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.824: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.824: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.825: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.825: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.825: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.825: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.825: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.825: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.826: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.826: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.826: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.826: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.826: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.826: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.826: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.827: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.827: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.827: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.827: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.827: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.827: Partial capture successful. Please touch the sensor again (4/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.827: Device reported enroll progress, reported 4 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.827: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.827: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.827: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.827: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.827: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.828: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.828: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.828: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.828: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.828: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.828: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.828: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.828: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.829: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.829: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.829: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.829: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.829: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.830: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.830: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.830: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.830: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.830: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.830: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.830: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.831: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.831: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.831: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.831: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.831: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.831: Partial capture successful. Please touch the sensor again (5/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.831: Device reported enroll progress, reported 5 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.831: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.831: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.831: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.831: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.831: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.832: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.832: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.832: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.832: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.832: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.832: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.832: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.833: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.833: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.833: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.833: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.833: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.833: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.833: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.834: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.834: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.834: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.834: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.834: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.834: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.834: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.835: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.835: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.835: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.835: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.835: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.835: Partial capture successful. Please touch the sensor again (6/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.835: Device reported enroll progress, reported 6 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.835: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.835: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.835: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.835: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.835: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.836: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.836: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.836: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.836: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.836: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.836: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.836: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.837: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.837: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.837: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.837: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.837: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.837: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.837: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.838: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.838: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.838: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.838: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.838: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.838: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.838: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.839: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.839: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.839: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.839: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.839: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.839: Partial capture successful. Please touch the sensor again (7/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.839: Device reported enroll progress, reported 7 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.839: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.839: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.839: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.839: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.839: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.840: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.840: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.840: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.840: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.840: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.840: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.840: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.840: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.841: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.841: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.841: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.841: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.841: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.841: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.842: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.842: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.842: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.842: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.842: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.842: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.842: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.843: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.843: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.843: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.843: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.843: Response suffix valid: NO 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.843: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.843: Response suffix valid: yes 374s (process:1893): libfprint-device-DEBUG: 05:08:14.843: Device reported enroll progress, reported 7 of 20 have been completed 374s listing - device should have prints 374s clear device storage 374s clear done 374s listing - device should be empty 374s enrolling 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 1, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 2, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 3, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 4, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 5, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 6, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 7, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 8, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 9, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 10, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 10, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 11, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 12, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 13, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 14, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 15, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 16, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 17, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 18, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 19, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 20, , None, None) 374s enroll done 374s listing - device should have 1 print 374s verifying 374s verify done 374s async identifying 374s indentification_done: 374s try to enroll duplicate 374s duplicate enroll attempt done 374s listing - device should still only have 1 print 374s enroll new finger 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 1, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 2, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 3, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 4, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 5, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 6, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 7, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))(process:1893): libfprint-SSM-DEBUG: 05:08:14.843: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.843: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.843: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.843: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.843: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.844: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.844: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.844: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.844: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.844: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.844: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.844: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.844: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.845: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.845: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.845: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.845: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.845: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.845: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.846: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.846: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.846: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.846: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.846: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.846: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.846: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.847: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.847: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.847: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.847: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.847: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.847: Partial capture successful. Please touch the sensor again (8/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.847: Device reported enroll progress, reported 8 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.847: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.847: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.847: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.847: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.847: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.848: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.848: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.848: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.848: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.848: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.848: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.848: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.848: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.849: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.849: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.849: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.849: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.849: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.849: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.849: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.849: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.849: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.850: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.850: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.850: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.850: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.851: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.851: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.851: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.851: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.851: Response suffix valid: NO 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.851: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.851: Response suffix valid: yes 374s (process:1893): libfprint-device-DEBUG: 05:08:14.851: Device reported enroll progress, reported 8 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.851: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.851: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.851: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.851: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.851: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.852: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.852: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.852: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.852: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.852: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.852: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.852: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.852: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.853: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.853: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.853: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.853: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.853: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.853: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.853: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.853: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.853: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.853: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.853: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.853: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.854: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.854: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.854: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.854: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.854: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.854: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.854: Partial capture successful. Please touch the sensor again (9/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.854: Device reported enroll progress, reported 9 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.855: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.855: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.855: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.855: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.855: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.856: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.856: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.856: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.856: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.856: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.856: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.856: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.856: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.857: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.857: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.857: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.857: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.857: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.857: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.857: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.857: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.857: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.857: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.857: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.857: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.858: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.858: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.858: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.858: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.858: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.858: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.858: Partial capture successful. Please touch the sensor again (10/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.858: Device reported enroll progress, reported 10 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.858: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.858: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.858: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.858: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.859: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.859: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.859: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.859: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.859: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.859: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.859: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.859: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.860: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.860: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.860: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.860: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.860: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.860: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.860: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.861: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.861: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.861: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.861: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.861: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.861: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.862: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.862: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.862: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.862: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.862: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.862: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.862: Partial capture successful. Please touch the sensor again (11/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.862: Device reported enroll progress, reported 11 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.862: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.862: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.862: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.862: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.863: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.863: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.863: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.863: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.863: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.863: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.863: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.863: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.864: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.864: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.864: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.864: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.864: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.864: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.865: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.865: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.865: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.865: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.865: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.865: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.865: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.866: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.866: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.866: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.866: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.866: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.866: Partial capture successful. Please touch the sensor again (12/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.866: Device reported enroll progress, reported 12 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.866: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.866: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.866: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.866: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.866: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.867: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.867: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.867: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.867: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.867: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.867: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.867: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.868: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.868: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.868: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.868: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.868: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.868: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.869: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.869: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.869: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.869: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.869: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.869: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.869: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.870: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.870: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.870: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.870: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.870: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.870: Partial capture successful. Please touch the sensor again (13/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.870: Device reported enroll progress, reported 13 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.870: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.870: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.870: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.870: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.870: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.871: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.871: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.871: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.871: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.871: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.871: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.871: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.871: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.872: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.872: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.872: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.872: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.872: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.873: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.873: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.873: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.873: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.873: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.873: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.873: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.874: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.874: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.874: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.874: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.874: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.874: Partial capture successful. Please touch the sensor again (14/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.874: Device reported enroll progress, reported 14 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.874: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.874: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.874: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.874: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.874: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.875: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.875: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.875: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.875: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.875: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.875: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.875: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.875: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.876: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.876: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.876: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.876: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.876: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.876: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.876: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.876: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.876: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.876: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.876: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.876: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.877: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.877: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.877: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.877: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.877: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.877: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.877: Partial capture successful. Please touch the sensor again (15/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.877: Device reported enroll progress, reported 15 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.878: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.878: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.878: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.878: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.878: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.879: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.879: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.879: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.879: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.879: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.879: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.879: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.879: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.880: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.880: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.880: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.880: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.880: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.880: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.880: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.880: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.880: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.880: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.880: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.880: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.881: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.882: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.882: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.882: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.882: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.882: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.882: Partial capture successful. Please touch the sensor again (16/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.882: Device reported enroll progress, reported 16 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.882: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.882: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.882: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.882: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.882: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.883: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.883: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.883: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.883: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.883: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.883: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.883: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.883: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.884: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.884: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.884: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.884: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.884: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.884: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.884: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.884: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.884: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.884: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.884: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.884: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.885: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.885: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.885: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.885: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.885: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.886: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.886: Partial capture successful. Please touch the sensor again (17/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.886: Device reported enroll progress, reported 17 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.886: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.886: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.886: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.886: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.886: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.887: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.887: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.887: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.887: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.887: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.887: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.887: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.887: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.888: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.888: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.888: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.888: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.888: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.888: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.888: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.888: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.888: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.888: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.888: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.888: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.889: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.889: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.889: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.889: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.889: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.889: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.889: Partial capture successful. Please touch the sensor again (18/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.889: Device reported enroll progress, reported 18 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.890: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.890: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.890: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.890: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.890: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.891: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.891: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.891: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.891: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.891: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.891: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.891: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.891: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.892: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.892: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.892: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.892: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.892: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.892: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.892: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.892: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.892: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.892: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.892: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.892: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.893: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.893: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.893: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.893: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.893: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.893: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.893: Partial capture successful. Please touch the sensor again (19/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.893: Device reported enroll progress, reported 19 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.893: [egismoc] ENROLL_STATES entering state 8 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.893: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.893: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.893: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.894: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.895: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.895: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.895: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.895: [egismoc] ENROLL_STATES entering state 9 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.895: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.895: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.895: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.895: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.896: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.896: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.896: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.896: [egismoc] ENROLL_STATES entering state 10 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.896: Wait for finger on sensor 374s (process:1893): libfprint-device-DEBUG: 05:08:14.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.896: Finger on sensor callback 374s (process:1893): libfprint-device-DEBUG: 05:08:14.896: Device reported finger status change: FP_FINGER_STATUS_PRESENT 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.896: [egismoc] ENROLL_STATES entering state 11 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.896: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.896: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.896: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.897: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.897: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.897: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.897: Read capture callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.897: Response prefix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.897: Response suffix valid: yes 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.897: Partial capture successful. Please touch the sensor again (20/20) 374s (process:1893): libfprint-device-DEBUG: 05:08:14.897: Device reported enroll progress, reported 20 of 20 have been completed 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.897: [egismoc] ENROLL_STATES entering state 12 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.897: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.897: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.897: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.898: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.898: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.898: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.898: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.898: [egismoc] ENROLL_STATES entering state 13 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.898: New fingerprint ID: FP1-00000000-7-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.898: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.898: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.898: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.899: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.900: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.900: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.900: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.900: [egismoc] ENROLL_STATES entering state 14 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.900: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.900: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.900: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.900: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.901: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.901: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.901: Task SSM next state callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.901: [egismoc] ENROLL_STATES entering state 15 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.901: Enrollment was successful! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.901: Device reported enroll completion 374s (process:1893): libfprint-device-DEBUG: 05:08:14.901: Device reported finger status change: FP_FINGER_STATUS_NONE 374s (process:1893): libfprint-device-DEBUG: 05:08:14.901: Print for finger FP_FINGER_RIGHT_INDEX enrolled 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.901: [egismoc] ENROLL_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.901: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.901: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.901: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.901: List 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.901: [egismoc] LIST_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.901: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.901: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.901: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.901: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.902: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.902: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.902: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.902: Device fingerprint 1: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.902: Device fingerprint 2: FP1-00000000-7-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.902: Number of currently enrolled fingerprints on the device is 2 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.902: [egismoc] LIST_STATES entering state 1 374s (process:1893): libfprint-device-DEBUG: 05:08:14.902: Device reported listing completion 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.902: [egismoc] LIST_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.902: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.902: Completing action FPI_DEVICE_ACTION_LIST in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.902: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.902: Delete 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.902: [egismoc] DELETE_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.902: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.902: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.902: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.903: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.903: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.903: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.903: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.903: Device fingerprint 1: FP1-00000000-2-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.903: Device fingerprint 2: FP1-00000000-7-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.903: Number of currently enrolled fingerprints on the device is 2 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.903: [egismoc] DELETE_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.903: Get delete command 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.903: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.903: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.903: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.903: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.904: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.904: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.904: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.904: Delete callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.904: Response prefix valid: yes 374s (process:1893): libfprint-device-DEBUG: 05:08:14.904: Device reported deletion completion 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.904: [egismoc] DELETE_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.905: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.905: Completing action FPI_DEVICE_ACTION_DELETE in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.905: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.905: List 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.905: [egismoc] LIST_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.905: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.905: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.905: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.905: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.906: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.906: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.906: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.906: Device fingerprint 1: FP1-00000000-7-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.906: Number of currently enrolled fingerprints on the device is 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.906: [egismoc] LIST_STATES entering state 1 374s (process:1893): libfprint-device-DEBUG: 05:08:14.906: Device reported listing completion 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.906: [egismoc] LIST_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.906: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.906: Completing action FPI_DEVICE_ACTION_LIST in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.906: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.906: Clear storage 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.906: [egismoc] DELETE_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.906: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.906: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.906: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.906: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.907: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.907: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.907: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.907: Device fingerprint 1: FP1-00000000-7-00000000-nobody 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.907: Number of currently enrolled fingerprints on the device is 1 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.907: [egismoc] DELETE_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.907: Get delete command 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.907: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.907: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.907: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.907: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.908: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.908: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.908: Delete callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.908: Response prefix valid: yes 374s (process:1893): libfprint-device-DEBUG: 05:08:14.908: Device reported deletion completion 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.908: [egismoc] DELETE_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.908: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.908: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.908: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.908: List 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.908: [egismoc] LIST_STATES entering state 0 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.908: Execute command and get response 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.908: Get check bytes 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.908: [egismoc] CMD_STATES entering state 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.909: [egismoc] CMD_STATES entering state 1 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.909: Command receive callback 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.909: [egismoc] CMD_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.909: List callback 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.909: Number of currently enrolled fingerprints on the device is 0 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.909: [egismoc] LIST_STATES entering state 1 374s (process:1893): libfprint-device-DEBUG: 05:08:14.909: Device reported listing completion 374s (process:1893): libfprint-SSM-DEBUG: 05:08:14.909: [egismoc] LIST_STATES completed successfully 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.909: Task SSM done 374s (process:1893): libfprint-device-DEBUG: 05:08:14.909: Completing action FPI_DEVICE_ACTION_LIST in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.909: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.909: Closing device 374s (process:1893): libfprint-egismoc-DEBUG: 05:08:14.909: Cancel 374s (process:1893): libfprint-device-DEBUG: 05:08:14.910: Device reported close completion 374s (process:1893): libfprint-device-DEBUG: 05:08:14.910: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 374s (process:1893): libfprint-device-DEBUG: 05:08:14.910: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 374s 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 8, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 9, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 10, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 11, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 12, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 13, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 14, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 15, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 16, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 17, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 18, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 19, , None, None) 374s finger status: 374s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf582f888 (FpiDeviceEgisMoc at 0xc5df38)>, 20, , None, None) 374s enroll new finger done 374s listing - device should have 2 prints 374s deleting first print 374s delete done 374s listing - device should only have second print 374s clear device storage 374s clear done 374s listing - device should be empty 374s ** (umockdev-run:1889): DEBUG: 05:08:14.935: umockdev.vala:154: Removing test bed /tmp/umockdev.QPL112 374s (umockdev-run:1889): GLib-DEBUG: 05:08:14.950: unsetenv() is not thread-safe and should not be used after threads are created 374s PASS: libfprint-2/driver-egismoc-0587.test 374s Running test: libfprint-2/fpi-assembling.test 374s TAP version 14 375s # random seed: R02Sf0a45730cdb81666c1ae1a3e94960f28 375s 1..1 375s # Start of assembling tests 375s # libfprint-assembling-DEBUG: calc delta completed in 0.110842 secs 375s # libfprint-assembling-DEBUG: calc delta completed in 0.110517 secs 375s # libfprint-assembling-DEBUG: errors: 0 rev: 130848 375s # libfprint-assembling-DEBUG: calc delta completed in 0.112611 secs 375s # libfprint-assembling-DEBUG: height is 310 375s ok 1 /assembling/frames 375s # End of assembling tests 375s PASS: libfprint-2/fpi-assembling.test 375s Running test: libfprint-2/driver-uru4000-msv2.test 375s ** (umockdev-run:1903): DEBUG: 05:08:15.370: umockdev.vala:127: Created udev test bed /tmp/umockdev.DQWH22 375s ** (umockdev-run:1903): DEBUG: 05:08:15.370: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 375s ** (umockdev-run:1903): DEBUG: 05:08:15.372: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 375s ** (umockdev-run:1903): DEBUG: 05:08:15.375: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DQWH22/dev/bus/usb/001/047 375s ** (umockdev-run:1903): DEBUG: 05:08:15.375: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 375s ** (umockdev-run:1903): DEBUG: 05:08:15.376: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 375s ** (umockdev-run:1903): DEBUG: 05:08:15.380: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DQWH22/dev/bus/usb/001/001 375s ** (umockdev-run:1903): DEBUG: 05:08:15.380: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 375s ** (umockdev-run:1903): DEBUG: 05:08:15.381: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 375s (process:1907): libfprint-context-DEBUG: 05:08:15.500: Initializing FpContext (libfprint version 1.94.9+tod1) 375s (process:1907): libfprint-tod-DEBUG: 05:08:15.500: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 375s (process:1907): libfprint-context-DEBUG: 05:08:15.503: No driver found for USB device 1D6B:0002 375s (process:1907): libfprint-device-DEBUG: 05:08:15.503: Device reported probe completion 375s (process:1907): libfprint-device-DEBUG: 05:08:15.503: Completing action FPI_DEVICE_ACTION_PROBE in idle! 375s (process:1907): libfprint-device-DEBUG: 05:08:15.503: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.508: Image device open completed 375s (process:1907): libfprint-device-DEBUG: 05:08:15.508: Device reported open completion 375s (process:1907): libfprint-device-DEBUG: 05:08:15.508: Completing action FPI_DEVICE_ACTION_OPEN in idle! 375s (process:1907): libfprint-device-DEBUG: 05:08:15.508: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1907): libfprint-device-DEBUG: 05:08:15.508: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.508: Activating image device 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.508: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.509: [uru4000] INIT_NUM_STATES entering state 0 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.509: read 1 regs at 7 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.509: reg value 3 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.509: [uru4000] INIT_NUM_STATES entering state 1 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.509: [uru4000] INIT_NUM_STATES entering state 3 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.509: set 83 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.510: [uru4000] INIT_NUM_STATES entering state 4 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.510: [uru4000] POWERUP_NUM_STATES entering state 0 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.510: [uru4000] POWERUP_NUM_STATES entering state 1 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.510: set 03 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.510: [uru4000] POWERUP_NUM_STATES entering state 2 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.510: read 1 regs at 7 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.511: reg value 83 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.511: [uru4000] POWERUP_NUM_STATES entering state 3 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.511: [uru4000] POWERUP_NUM_STATES entering state 4 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.521: [uru4000] POWERUP_NUM_STATES entering state 5 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.521: 130954515114: ../libfprint/drivers/uru4000.c:326 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.522: [uru4000] POWERUP_NUM_STATES entering state 6 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.522: [uru4000] POWERUP_NUM_STATES entering state 1 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.522: set 03 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.523: [uru4000] POWERUP_NUM_STATES entering state 2 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.523: read 1 regs at 7 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.523: reg value 3 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.523: [uru4000] POWERUP_NUM_STATES entering state 3 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.523: [uru4000] POWERUP_NUM_STATES completed successfully 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.523: [uru4000] INIT_NUM_STATES entering state 5 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.524: recv irq type 56aa 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.524: late scanpwr interrupt 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.524: [uru4000] INIT_NUM_STATES entering state 6 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.524: [uru4000] INIT_NUM_STATES entering state 7 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.524: read 16 regs at f0 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.525: reg value 50 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.525: [uru4000] INIT_NUM_STATES entering state 8 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.525: Versions 0059 and 0034 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.525: [uru4000] INIT_NUM_STATES completed successfully 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.525: Image device activation completed 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.525: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.525: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.525: wait finger on 375s (process:1907): libfprint-device-DEBUG: 05:08:15.525: Device reported finger status change: FP_FINGER_STATUS_NEEDED 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.526: recv irq type 0101 375s (process:1907): libfprint-device-DEBUG: 05:08:15.526: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.526: Image device reported finger status: on 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.526: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.526: starting capture 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.526: Image encryption seed: 1374298404 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.526: [uru4000] IMAGING_NUM_STATES entering state 0 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.531: [uru4000] IMAGING_NUM_STATES entering state 1 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.531: hw header lines 289 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.531: dev2: 10849 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.531: image seems to be encrypted 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.532: [uru4000] IMAGING_NUM_STATES entering state 2 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.532: read 4 regs at 34 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: reg value 7b 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.533: [uru4000] IMAGING_NUM_STATES entering state 3 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: encryption id 05 -> key db896f5f 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: 0 02 67 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: decoding 67 lines 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: 1 00 1 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: skipping 1 lines 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: 2 02 49 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: decoding 49 lines 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: 3 01 1 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: skipping 1 lines 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: 4 00 1 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: skipping 1 lines 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: 5 02 49 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.533: decoding 49 lines 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.534: 6 00 1 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.534: skipping 1 lines 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.534: 7 02 121 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.534: decoding 121 lines 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.534: [uru4000] IMAGING_NUM_STATES entering state 4 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.534: Image device captured an image 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.536: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 375s (process:1907): libfprint-device-DEBUG: 05:08:15.536: Device reported finger status change: FP_FINGER_STATUS_PRESENT 375s (process:1907): libfprint-SSM-DEBUG: 05:08:15.536: [uru4000] IMAGING_NUM_STATES completed successfully 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.536: await finger off 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.538: recv irq type 0200 375s (process:1907): libfprint-device-DEBUG: 05:08:15.538: Device reported finger status change: FP_FINGER_STATUS_NONE 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.538: Image device reported finger status: off 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.538: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.538: Deactivating image device 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.538: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.538: deactivating 375s (process:1907): libfprint-uru4000-DEBUG: 05:08:15.539: cancelled 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.539: Image device deactivation completed 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.539: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 375s (process:1907): libfprint-image-DEBUG: 05:08:15.582: Minutiae scan completed in 0.045444 secs 375s (process:1907): libfprint-device-DEBUG: 05:08:15.582: Device reported capture completion 375s (process:1907): libfprint-device-DEBUG: 05:08:15.582: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 375s (process:1907): libfprint-device-DEBUG: 05:08:15.582: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 375s (process:1907): libfprint-image_device-DEBUG: 05:08:15.583: Image device close completed 375s (process:1907): libfprint-device-DEBUG: 05:08:15.583: Device reported close completion 375s (process:1907): libfprint-device-DEBUG: 05:08:15.583: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 375s (process:1907): libfprint-device-DEBUG: 05:08:15.583: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 375s ** (umockdev-run:1903): DEBUG: 05:08:15.776: umockdev.vala:154: Removing test bed /tmp/umockdev.DQWH22 375s (umockdev-run:1903): GLib-DEBUG: 05:08:15.782: unsetenv() is not thread-safe and should not be used after threads are created 375s Comparing PNGs /tmp/libfprint-umockdev-test-vhyd8446/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-msv2/capture.png 375s PASS: libfprint-2/driver-uru4000-msv2.test 375s Running test: libfprint-2/driver-fpcmoc.test 375s ** (umockdev-run:1916): DEBUG: 05:08:15.881: umockdev.vala:127: Created udev test bed /tmp/umockdev.EBJ512 375s ** (umockdev-run:1916): DEBUG: 05:08:15.882: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-1 375s ** (umockdev-run:1916): DEBUG: 05:08:15.884: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-1 (subsystem usb) 375s ** (umockdev-run:1916): DEBUG: 05:08:15.888: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.EBJ512/dev/bus/usb/001/019 375s ** (umockdev-run:1916): DEBUG: 05:08:15.888: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 375s ** (umockdev-run:1916): DEBUG: 05:08:15.890: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 375s ** (umockdev-run:1916): DEBUG: 05:08:15.893: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.EBJ512/dev/bus/usb/001/001 375s ** (umockdev-run:1916): DEBUG: 05:08:15.893: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 375s ** (umockdev-run:1916): DEBUG: 05:08:15.894: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 376s (process:1920): libfprint-context-DEBUG: 05:08:16.003: Initializing FpContext (libfprint version 1.94.9+tod1) 376s (process:1920): libfprint-tod-DEBUG: 05:08:16.003: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 376s (process:1920): libfprint-DEBUG: 05:08:16.006: fpi_device_fpcmoc_init enter --> 376s (process:1920): libfprint-DEBUG: 05:08:16.006: 130955000093: ../libfprint/drivers/fpcmoc/fpc.c:1875 376s (process:1920): libfprint-context-DEBUG: 05:08:16.006: No driver found for USB device 1D6B:0002 376s (process:1920): libfprint-DEBUG: 05:08:16.007: fpc_dev_probe enter --> 376s (process:1920): libfprint-DEBUG: 05:08:16.010: Device name: FPC L:0001 FW:127010 376s (process:1920): libfprint-device-DEBUG: 05:08:16.010: Device reported probe completion 376s (process:1920): libfprint-device-DEBUG: 05:08:16.010: Completing action FPI_DEVICE_ACTION_PROBE in idle! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.010: Not updating temperature model, device can run continuously! 376s (process:1920): libfprint-DEBUG: 05:08:16.012: fpc_dev_open enter --> 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.012: [fpcmoc] FP_INIT_NUM_STATES entering state 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.012: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.012: fpc_send_ctrl_cmd CMD: 0x1, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-DEBUG: 05:08:16.013: fpc_cmd_receive_cb current ssm request: 1 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.013: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.014: fpc_cmd_receive_cb current ssm request: 1 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.014: fpc_cmd_receive_cb recv evt data length: 38 376s (process:1920): libfprint-DEBUG: 05:08:16.014: fpc_evt_cb INIT: status=0, Sensor = 1523, HWID = 0x1711, WxH = 96 x 96 376s (process:1920): libfprint-DEBUG: 05:08:16.014: fpc_evt_cb INIT: FW version: 1.27.0.10 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.014: [fpcmoc] FP_INIT_NUM_STATES entering state 1 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.014: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.014: fpc_send_ctrl_cmd CMD: 0x60, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.014: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.015: fpc_cmd_receive_cb current ssm request: 96 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.015: fpc_init_load_db_cb got dbid size: 16 376s (process:1920): libfprint-DEBUG: 05:08:16.015: fpc_init_load_db_cb dbid: 0xa981b581-adfc-e643-a0d0-88c2138092f7 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.015: [fpcmoc] FP_INIT_NUM_STATES completed successfully 376s (process:1920): libfprint-device-DEBUG: 05:08:16.015: Device reported open completion 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.015: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-device-DEBUG: 05:08:16.015: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.015: Not updating temperature model, device can run continuously! 376s (process:1920): libfprint-DEBUG: 05:08:16.015: fpc_dev_clear_storage enter --> 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.015: [fpcmoc] Clear storage entering state 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.015: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.015: fpc_send_ctrl_cmd CMD: 0x62, value: 0x0, index: 0 type: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.015: fpc_cmd_receive_cb current ssm request: 98 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.015: [fpcmoc] Clear storage entering state 1 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.015: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.015: fpc_send_ctrl_cmd CMD: 0x60, value: 0x1, index: 0 type: 1 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.016: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.016: fpc_cmd_receive_cb current ssm request: 96 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.016: [fpcmoc] Clear storage completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.016: Clear Storage complete! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.016: Device reported deletion completion 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.016: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-device-DEBUG: 05:08:16.016: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.016: Not updating temperature model, device can run continuously! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.017: Not updating temperature model, device can run continuously! 376s (process:1920): libfprint-DEBUG: 05:08:16.017: fpc_dev_enroll enter --> 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.017: [fpcmoc] enroll entering state 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.017: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.017: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-DEBUG: 05:08:16.018: fpc_cmd_receive_cb current ssm request: 112 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.018: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.018: fpc_cmd_receive_cb current ssm request: 112 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.018: fpc_cmd_receive_cb recv evt data length: 790 376s (process:1920): libfprint-DEBUG: 05:08:16.018: fpc_evt_cb Enum Fids: status = 0, NumFids = 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.018: [fpcmoc] enroll entering state 1 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.018: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.018: fpc_send_ctrl_cmd CMD: 0x67, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.019: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.019: fpc_cmd_receive_cb current ssm request: 103 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.019: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-device-DEBUG: 05:08:16.019: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.019: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.019: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.019: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.019: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.019: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.020: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.020: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.020: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.020: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.020: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.020: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.020: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.020: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.021: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.021: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.021: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.021: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.021: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.021: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.021: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.021: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.021: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.021: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.022: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.022: Enrol Update status: 1, remaining: 11 376s (process:1920): libfprint-device-DEBUG: 05:08:16.022: Device reported enroll progress, reported 1 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.022: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.022: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.022: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.022: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.022: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.022: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.023: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.023: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.023: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.023: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.023: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.023: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.023: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.023: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.024: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.024: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.024: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.024: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.024: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.024: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.024: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.024: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.024: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.025: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.025: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.025: Enrol Update status: 1, remaining: 10 376s (process:1920): libfprint-device-DEBUG: 05:08:16.025: Device reported enroll progress, reported 2 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.025: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.025: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.025: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.025: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.025: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.025: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.026: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.026: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.026: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.026: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.026: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.026: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.026: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.026: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.027: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.027: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.027: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.027: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.027: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.027: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.027: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.027: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.027: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.028: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.028: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.028: Enrol Update status: 1, remaining: 9 376s (process:1920): libfprint-device-DEBUG: 05:08:16.028: Device reported enroll progress, reported 3 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.028: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.028: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.028: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.028: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.028: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.028: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.029: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.029: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.029: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.029: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.029: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.029: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.029: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.029: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.030: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.030: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.030: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.030: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.030: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.030: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.030: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.030: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.030: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.031: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.031: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.031: Enrol Update status: 1, remaining: 8 376s (process:1920): libfprint-device-DEBUG: 05:08:16.031: Device reported enroll progress, reported 4 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.031: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.031: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.031: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.031: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.032: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.032: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.032: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.032: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.032: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.032: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.032: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.032: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.032: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.033: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.033: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.033: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.034: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.034: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.034: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.034: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.034: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.034: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.034: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.034: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.034: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.034: Enrol Update status: 1, remaining: 7 376s (process:1920): libfprint-device-DEBUG: 05:08:16.034: Device reported enroll progress, reported 5 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.034: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.034: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.034: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.035: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.035: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.035: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.035: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.035: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.035: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.035: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.035: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.035: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.035: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.036: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.036: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.036: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.037: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.037: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.037: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.037: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.037: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.037: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.037: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.037: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.037: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.037: Enrol Update status: 5, remaining: 7 376s (process:1920): libfprint-DEBUG: 05:08:16.037: Sample overlapping ratio is too High 376s (process:1920): libfprint-device-DEBUG: 05:08:16.037: Device reported enroll progress, reported 5 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.037: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.037: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.037: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.038: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.038: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.038: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.039: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.039: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.039: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.039: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.039: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.039: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.039: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.039: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.039: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.039: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.040: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.040: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.040: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.040: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.040: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.040: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.040: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.040: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.041: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.041: Enrol Update status: 1, remaining: 6 376s (process:1920): libfprint-device-DEBUG: 05:08:16.041: Device reported enroll progress, reported 6 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.041: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.041: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.041: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.041: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.041: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.041: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.042: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.042: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.042: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.042: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.042: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.042: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.042: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.042: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.042: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.043: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.043: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.043: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.043: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.043: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.043: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.043: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.043: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.044: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.044: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.044: Enrol Update status: 1, remaining: 5 376s (process:1920): libfprint-device-DEBUG: 05:08:16.044: Device reported enroll progress, reported 7 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.044: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.044: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.044: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.044: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.044: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.044: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.045: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.045: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.045: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.045: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.045: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.045: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.045: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.046: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.046: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.046: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.047: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.047: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.047: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.047: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.047: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.047: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.047: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.047: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.047: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.047: Enrol Update status: 5, remaining: 5 376s (process:1920): libfprint-DEBUG: 05:08:16.047: Sample overlapping ratio is too High 376s (process:1920): libfprint-device-DEBUG: 05:08:16.047: Device reported enroll progress, reported 7 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.047: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.047: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.047: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.048: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.048: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.048: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.049: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.049: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.049: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.049: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.049: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.049: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.049: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.049: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.049: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.049: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.050: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.050: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.050: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.050: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.050: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.050: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.050: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.050: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.051: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.051: Enrol Update status: 1, remaining: 4 376s (process:1920): libfprint-device-DEBUG: 05:08:16.051: Device reported enroll progress, reported 8 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.051: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.051: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.051: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.051: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.051: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.051: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.052: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.052: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.052: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.052: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.052: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.052: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.052: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.052: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.053: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.053: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.053: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.053: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.053: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.053: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.053: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.053: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.053: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.054: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.054: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.054: Enrol Update status: 1, remaining: 3 376s (process:1920): libfprint-device-DEBUG: 05:08:16.054: Device reported enroll progress, reported 9 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.054: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.054: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.054: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.054: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.055: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.055: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.055: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.055: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.055: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.055: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.055: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.055: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.055: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.056: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.056: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.056: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.057: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.057: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.057: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.057: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.057: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.057: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.057: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.057: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.057: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.057: Enrol Update status: 1, remaining: 2 376s (process:1920): libfprint-device-DEBUG: 05:08:16.057: Device reported enroll progress, reported 10 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.057: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.057: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.057: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.058: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.058: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.058: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.059: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.059: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.059: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.059: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.059: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.059: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.059: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.059: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.059: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.059: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.060: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.060: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.060: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.060: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.060: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.060: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.060: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.061: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.061: Enrol Update status: 5, remaining: 2 376s (process:1920): libfprint-DEBUG: 05:08:16.061: Sample overlapping ratio is too High 376s (process:1920): libfprint-device-DEBUG: 05:08:16.061: Device reported enroll progress, reported 10 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.061: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.061: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.061: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.061: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.061: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.061: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.062: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.062: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.062: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.062: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.062: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.062: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.062: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.063: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.063: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.063: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.063: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.063: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.063: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.063: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.063: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.063: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.064: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.064: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.064: Enrol Update status: 1, remaining: 1 376s (process:1920): libfprint-device-DEBUG: 05:08:16.064: Device reported enroll progress, reported 11 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.064: [fpcmoc] enroll entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.064: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.064: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.064: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.065: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.065: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.065: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.065: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.065: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.065: [fpcmoc] enroll entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.065: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.065: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.066: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.066: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.066: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.067: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.067: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.067: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.067: [fpcmoc] enroll entering state 4 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.067: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.067: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.067: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.067: fpc_cmd_receive_cb current ssm request: 104 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.067: Enrol Update status: 0, remaining: 0 376s (process:1920): libfprint-device-DEBUG: 05:08:16.067: Device reported enroll progress, reported 12 of 25 have been completed 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.067: [fpcmoc] enroll entering state 5 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.067: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.067: fpc_send_ctrl_cmd CMD: 0x69, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.068: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.068: fpc_cmd_receive_cb current ssm request: 105 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.068: Enrol End status: 0, fid: 0x0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.068: [fpcmoc] enroll entering state 6 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.068: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.068: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.068: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.069: fpc_cmd_receive_cb current ssm request: 107 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.069: [fpcmoc] enroll entering state 7 376s (process:1920): libfprint-DEBUG: 05:08:16.069: user_id: FP1-00000000-0-00000000-nobody, finger: 0xf5 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.069: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.069: fpc_send_ctrl_cmd CMD: 0x6a, value: 0x0, index: 0 type: 1 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.069: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.069: fpc_cmd_receive_cb current ssm request: 106 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.069: [fpcmoc] enroll entering state 8 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.069: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.069: fpc_send_ctrl_cmd CMD: 0x61, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.070: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.070: fpc_cmd_receive_cb current ssm request: 97 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.070: [fpcmoc] enroll entering state 9 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.070: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.070: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.070: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.070: fpc_cmd_receive_cb current ssm request: 3 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.070: fpc_do_abort_cb Do abort for reasons 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.070: [fpcmoc] enroll entering state 10 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.070: [fpcmoc] enroll completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.070: Enrollment complete! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.070: Device reported enroll completion 376s (process:1920): libfprint-device-DEBUG: 05:08:16.070: Device reported finger status change: FP_FINGER_STATUS_NONE 376s (process:1920): libfprint-device-DEBUG: 05:08:16.070: Print for finger FP_FINGER_UNKNOWN enrolled 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.070: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-device-DEBUG: 05:08:16.070: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.070: Not updating temperature model, device can run continuously! 376s (process:1920): libfprint-DEBUG: 05:08:16.071: fpc_dev_template_list enter --> 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.071: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.071: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-DEBUG: 05:08:16.071: fpc_cmd_receive_cb current ssm request: 112 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.071: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.072: fpc_cmd_receive_cb current ssm request: 112 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.072: fpc_cmd_receive_cb recv evt data length: 790 376s (process:1920): libfprint-DEBUG: 05:08:16.072: Query templates complete! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.072: Device reported listing completion 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.072: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-device-DEBUG: 05:08:16.072: Completing action FPI_DEVICE_ACTION_LIST in idle! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.072: Not updating temperature model, device can run continuously! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.072: Not updating temperature model, device can run continuously! 376s (process:1920): libfprint-DEBUG: 05:08:16.072: fpc_dev_verify_identify enter --> 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.072: [fpcmoc] verify_identify entering state 0 376s (process:1920): libfprint-device-DEBUG: 05:08:16.072: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.072: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.072: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-DEBUG: 05:08:16.073: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.073: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.074: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.074: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.074: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.074: [fpcmoc] verify_identify entering state 1 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.074: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.074: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.074: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.074: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.074: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.075: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.075: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.075: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.075: [fpcmoc] verify_identify entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.075: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.075: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.075: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.076: fpc_cmd_receive_cb current ssm request: 107 state: 0 376s (process:1920): libfprint-device-DEBUG: 05:08:16.076: Device reported verify result 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.076: [fpcmoc] verify_identify entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.076: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.076: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.076: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.076: fpc_cmd_receive_cb current ssm request: 3 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.076: fpc_do_abort_cb Do abort for reasons 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.076: [fpcmoc] verify_identify completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.076: Verify_identify complete! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.076: Device reported verify completion 376s (process:1920): libfprint-device-DEBUG: 05:08:16.076: Device reported finger status change: FP_FINGER_STATUS_NONE 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.076: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-device-DEBUG: 05:08:16.076: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.076: Not updating temperature model, device can run continuously! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.077: Not updating temperature model, device can run continuously! 376s (process:1920): libfprint-DEBUG: 05:08:16.077: fpc_dev_verify_identify enter --> 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.077: [fpcmoc] verify_identify entering state 0 376s (process:1920): libfprint-device-DEBUG: 05:08:16.077: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.077: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.077: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 376s (process:1920): libfprint-DEBUG: 05:08:16.078: fpc_cmd_receive_cb current ssm request: 2 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.078: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.078: fpc_cmd_receive_cb current ssm request: 2 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.078: fpc_cmd_receive_cb recv evt data length: 12 376s (process:1920): libfprint-DEBUG: 05:08:16.078: fpc_evt_cb Got finger down event (0) 376s (process:1920): libfprint-device-DEBUG: 05:08:16.078: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.078: [fpcmoc] verify_identify entering state 1 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.078: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.078: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.079: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.079: fpc_cmd_receive_cb current ssm request: 9 state: 0 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.079: [fpcmoc] FP_CMD_NUM_STATES entering state 1 376s (process:1920): libfprint-DEBUG: 05:08:16.080: fpc_cmd_receive_cb current ssm request: 9 state: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.080: fpc_cmd_receive_cb recv evt data length: 24 376s (process:1920): libfprint-DEBUG: 05:08:16.080: fpc_evt_cb Got capture event 376s (process:1920): libfprint-device-DEBUG: 05:08:16.080: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.080: [fpcmoc] verify_identify entering state 2 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.080: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.080: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.080: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.080: fpc_cmd_receive_cb current ssm request: 107 state: 0 376s (process:1920): libfprint-device-DEBUG: 05:08:16.080: Device reported identify result 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.080: [fpcmoc] verify_identify entering state 3 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.080: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.080: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.081: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.081: fpc_cmd_receive_cb current ssm request: 3 state: 0 376s (process:1920): libfprint-DEBUG: 05:08:16.081: fpc_do_abort_cb Do abort for reasons 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.081: [fpcmoc] verify_identify completed successfully 376s (process:1920): libfprint-DEBUG: 05:08:16.081: Verify_identify complete! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.081: Device reported identify completion 376s (process:1920): libfprint-device-DEBUG: 05:08:16.081: Device reported finger status change: FP_FINGER_STATUS_NONE 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.081: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-device-DEBUG: 05:08:16.081: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.081: Not updating temperature model, device can run continuously! 376s (process:1920): libfprint-DEBUG: 05:08:16.082: fpc_dev_template_delete enter --> 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.082: [fpcmoc] FP_CMD_NUM_STATES entering state 0 376s (process:1920): libfprint-DEBUG: 05:08:16.082: fpc_send_ctrl_cmd CMD: 0x63, value: 0x0, index: 0 type: 1 376s (process:1920): libfprint-DEBUG: 05:08:16.082: fpc_dev_template_delete exit <-- 376s (process:1920): libfprint-DEBUG: 05:08:16.082: fpc_cmd_receive_cb current ssm request: 99 state: 0 376s (process:1920): libfprint-device-DEBUG: 05:08:16.082: Device reported deletion completion 376s (process:1920): libfprint-SSM-DEBUG: 05:08:16.082: [fpcmoc] FP_CMD_NUM_STATES completed successfully 376s (process:1920): libfprint-device-DEBUG: 05:08:16.082: Completing action FPI_DEVICE_ACTION_DELETE in idle! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.083: Not updating temperature model, device can run continuously! 376s (process:1920): libfprint-DEBUG: 05:08:16.083: fpc_dev_close enter --> 376s (process:1920): libfprint-device-DEBUG: 05:08:16.083: Device reported close completion 376s (process:1920): libfprint-device-DEBUG: 05:08:16.083: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s (process:1920): libfprint-device-DEBUG: 05:08:16.083: Not updating temperature model, device can run continuously! 376s Clear 376s Clear done 376s enrolling 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 1, None, None, None) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 2, None, None, None) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 3, None, None, None) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 4, None, None, None) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 5, None, None, None) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 5, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 6, None, None, None) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 7, None, None, None) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 7, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 8, None, None, None) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 9, None, None, None) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 10, None, None, None) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 10, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 11, None, None, None) 376s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xe74bf4e8 (FpiDeviceFpcMoc at 0x122ffc8)>, 12, None, None, None) 376s enroll done 376s listing 376s listing done 376s verifying 376s verify done 376s async identifying 376s indentification_done: 376s deleting 376s delete done 376s ** (umockdev-run:1916): DEBUG: 05:08:16.111: umockdev.vala:154: Removing test bed /tmp/umockdev.EBJ512 376s (umockdev-run:1916): GLib-DEBUG: 05:08:16.119: unsetenv() is not thread-safe and should not be used after threads are created 376s PASS: libfprint-2/driver-fpcmoc.test 376s Running test: libfprint-2/driver-upektc_img.test 376s ** (umockdev-run:1928): DEBUG: 05:08:16.176: umockdev.vala:127: Created udev test bed /tmp/umockdev.AGFG22 376s ** (umockdev-run:1928): DEBUG: 05:08:16.177: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 376s ** (umockdev-run:1928): DEBUG: 05:08:16.179: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 (subsystem usb) 376s ** (umockdev-run:1928): DEBUG: 05:08:16.184: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.AGFG22/dev/bus/usb/001/003 376s ** (umockdev-run:1928): DEBUG: 05:08:16.184: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1 376s ** (umockdev-run:1928): DEBUG: 05:08:16.186: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1 (subsystem usb) 376s ** (umockdev-run:1928): DEBUG: 05:08:16.189: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.AGFG22/dev/bus/usb/001/002 376s ** (umockdev-run:1928): DEBUG: 05:08:16.190: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1 376s ** (umockdev-run:1928): DEBUG: 05:08:16.191: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1 (subsystem usb) 376s ** (umockdev-run:1928): DEBUG: 05:08:16.195: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.AGFG22/dev/bus/usb/001/001 376s ** (umockdev-run:1928): DEBUG: 05:08:16.195: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0 376s ** (umockdev-run:1928): DEBUG: 05:08:16.196: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0 (subsystem pci) 376s (process:1932): libfprint-context-DEBUG: 05:08:16.316: Initializing FpContext (libfprint version 1.94.9+tod1) 376s (process:1932): libfprint-tod-DEBUG: 05:08:16.316: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 376s (process:1932): libfprint-context-DEBUG: 05:08:16.320: No driver found for USB device 8087:0020 376s (process:1932): libfprint-context-DEBUG: 05:08:16.320: No driver found for USB device 1D6B:0002 376s (process:1932): libfprint-device-DEBUG: 05:08:16.321: Device reported probe completion 376s (process:1932): libfprint-device-DEBUG: 05:08:16.321: Completing action FPI_DEVICE_ACTION_PROBE in idle! 376s (process:1932): libfprint-device-DEBUG: 05:08:16.321: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.323: Image device open completed 376s (process:1932): libfprint-device-DEBUG: 05:08:16.323: Device reported open completion 376s (process:1932): libfprint-device-DEBUG: 05:08:16.323: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s (process:1932): libfprint-device-DEBUG: 05:08:16.323: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s (process:1932): libfprint-device-DEBUG: 05:08:16.323: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.323: Activating image device 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.323: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.323: [upektc_img] ACTIVATE_NUM_STATES entering state 0 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.324: [upektc_img] ACTIVATE_NUM_STATES entering state 1 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.325: [upektc_img] ACTIVATE_NUM_STATES entering state 2 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.325: [upektc_img] ACTIVATE_NUM_STATES entering state 3 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.326: [upektc_img] ACTIVATE_NUM_STATES entering state 4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.327: [upektc_img] ACTIVATE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.327: [upektc_img] ACTIVATE_NUM_STATES entering state 6 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.328: [upektc_img] ACTIVATE_NUM_STATES entering state 7 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.328: [upektc_img] ACTIVATE_NUM_STATES entering state 8 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.329: [upektc_img] ACTIVATE_NUM_STATES entering state 9 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.330: [upektc_img] ACTIVATE_NUM_STATES entering state 10 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.330: [upektc_img] ACTIVATE_NUM_STATES entering state 11 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.331: Sensor type : TCS4x, width x height: 192 x 512 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.331: [upektc_img] ACTIVATE_NUM_STATES completed successfully 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.331: Image device activation completed 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.331: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.331: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 376s (process:1932): libfprint-device-DEBUG: 05:08:16.331: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.331: [upektc_img] CAPTURE_NUM_STATES entering state 0 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.331: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.332: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.332: 18th byte is 0c 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.332: [upektc_img] CAPTURE_NUM_STATES entering state 3 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.332: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.333: request completed, len: 0040 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.333: [upektc_img] CAPTURE_NUM_STATES entering state 4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.334: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.334: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.334: 18th byte is 00 376s (process:1932): libfprint-device-DEBUG: 05:08:16.334: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.335: [upektc_img] CAPTURE_NUM_STATES entering state 3 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.335: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.336: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.336: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.336: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.336: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.336: request completed, len: 07c4 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.336: Image device reported finger status: on 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.336: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.336: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.337: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.337: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.337: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.337: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.337: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.338: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.338: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.339: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.339: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.339: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.339: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.339: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.340: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.340: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.340: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.341: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.341: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.341: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.341: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.341: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.341: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.342: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.342: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.342: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.342: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.342: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.343: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.343: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.343: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.344: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.344: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.344: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.344: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.345: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.345: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.345: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.346: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.346: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.346: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.346: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.346: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.346: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.347: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.347: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.347: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.347: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.347: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.348: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.348: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.348: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.349: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.349: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.349: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.349: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.350: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.350: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.350: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.351: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.351: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.351: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.351: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.351: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.351: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.353: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.354: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.354: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.354: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.354: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.354: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.354: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.355: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.356: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.356: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.356: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.356: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.357: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.357: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.357: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.358: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.358: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.358: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.358: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.359: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.359: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.359: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.360: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.360: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.360: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.360: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.361: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.361: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.362: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.362: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.362: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.362: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.362: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.363: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.363: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.364: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.364: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.364: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.364: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.364: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.365: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.365: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.366: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.366: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.366: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.366: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.366: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.367: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.367: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.368: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.369: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.369: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.369: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.369: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.369: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.369: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.370: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.371: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.371: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.371: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.371: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.372: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.372: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.372: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.373: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.373: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.373: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.373: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.374: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.374: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.374: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.375: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.375: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.375: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.375: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.376: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.376: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.376: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.377: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.377: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.377: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.377: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.378: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.378: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.378: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.379: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.379: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.379: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.379: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.379: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.379: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.380: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.381: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.381: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.381: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.381: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.381: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.382: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.382: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.383: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.383: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.383: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.383: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.383: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.383: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.384: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.384: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.384: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.384: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.384: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.385: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.385: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.386: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.386: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.386: response_size is 2052, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.386: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.386: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.387: request completed, len: 07c4 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.387: [upektc_img] CAPTURE_NUM_STATES entering state 5 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.387: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.388: request completed, len: 0040 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.388: response_size is 186, actual_length is 64 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.388: Waiting for rest of transfer 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.388: [upektc_img] CAPTURE_NUM_STATES entering state 1 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.389: request completed, len: 007a 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.389: Image size is 55296 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.389: Image device captured an image 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.390: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 376s (process:1932): libfprint-device-DEBUG: 05:08:16.390: Device reported finger status change: FP_FINGER_STATUS_PRESENT 376s (process:1932): libfprint-device-DEBUG: 05:08:16.390: Device reported finger status change: FP_FINGER_STATUS_NONE 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.390: Image device reported finger status: off 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.390: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.390: Deactivating image device 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.390: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.390: [upektc_img] CAPTURE_NUM_STATES completed successfully 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.390: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.391: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 376s (process:1932): libfprint-SSM-DEBUG: 05:08:16.391: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 376s (process:1932): libfprint-upektc_img-DEBUG: 05:08:16.391: Deactivate completed 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.391: Image device deactivation completed 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.391: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 376s (process:1932): libfprint-image-DEBUG: 05:08:16.403: Minutiae scan completed in 0.012591 secs 376s (process:1932): libfprint-device-DEBUG: 05:08:16.403: Device reported capture completion 376s (process:1932): libfprint-device-DEBUG: 05:08:16.403: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 376s (process:1932): libfprint-device-DEBUG: 05:08:16.403: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s (process:1932): libfprint-image_device-DEBUG: 05:08:16.404: Image device close completed 376s (process:1932): libfprint-device-DEBUG: 05:08:16.404: Device reported close completion 376s (process:1932): libfprint-device-DEBUG: 05:08:16.404: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s (process:1932): libfprint-device-DEBUG: 05:08:16.404: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ** (umockdev-run:1928): DEBUG: 05:08:16.511: umockdev.vala:154: Removing test bed /tmp/umockdev.AGFG22 376s (umockdev-run:1928): GLib-DEBUG: 05:08:16.520: unsetenv() is not thread-safe and should not be used after threads are created 376s Comparing PNGs /tmp/libfprint-umockdev-test-f24nfcz0/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img/capture.png 376s PASS: libfprint-2/driver-upektc_img.test 376s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 376s TAP version 14 376s # random seed: R02Sebdedd201f6be598ac75ace0181c08e2 376s 1..97 376s # Start of driver tests 376s ok 1 /driver/get_driver 376s ok 2 /driver/get_device_id 376s ok 3 /driver/get_name 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 4 /driver/is_open 376s ok 5 /driver/get_nr_enroll_stages 376s ok 6 /driver/set_nr_enroll_stages 376s ok 7 /driver/supports_identify 376s ok 8 /driver/supports_capture 376s ok 9 /driver/has_storage 376s ok 10 /driver/do_not_support_identify 376s ok 11 /driver/do_not_support_capture 376s ok 12 /driver/has_not_storage 376s ok 13 /driver/get_usb_device 376s ok 14 /driver/get_virtual_env 376s ok 15 /driver/get_driver_data 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 376s # 376s # libfprint-device-DEBUG: Device reported probe completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s ok 16 /driver/initial_features 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 376s # 376s # libfprint-device-DEBUG: Device reported probe completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 17 /driver/probe 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 18 /driver/open 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 19 /driver/close 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 376s # 376s # libfprint-device-DEBUG: Device reported enroll completion 376s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 20 /driver/enroll 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 376s # 376s # libfprint-device-DEBUG: Device reported verify result 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 21 /driver/verify 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 376s # 376s # libfprint-device-DEBUG: Device reported identify result 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 22 /driver/identify 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 376s # 376s # libfprint-device-DEBUG: Device reported capture completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 23 /driver/capture 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 376s # 376s # libfprint-device-DEBUG: Device reported listing completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 24 /driver/list 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 376s # 376s # libfprint-device-DEBUG: Device reported deletion completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 25 /driver/delete 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 376s # 376s # libfprint-device-DEBUG: Device reported deletion completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 26 /driver/clear_storage 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 376s # 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 376s # 376s # libfprint-device-DEBUG: Device reported deletion completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 27 /driver/cancel 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 376s # 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 376s # 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 376s # 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 376s # 376s # libfprint-device-DEBUG: Device reported verify result 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 28 /driver/critical 376s ok 29 /driver/get_current_action 376s ok 30 /driver/timeout 376s ok 31 /driver/error_types 376s ok 32 /driver/retry_error_types 376s # Start of get_scan_type tests 376s ok 33 /driver/get_scan_type/press 376s ok 34 /driver/get_scan_type/swipe 376s # End of get_scan_type tests 376s # Start of set_scan_type tests 376s ok 35 /driver/set_scan_type/press 376s ok 36 /driver/set_scan_type/swipe 376s # End of set_scan_type tests 376s # Start of finger_status tests 376s ok 37 /driver/finger_status/inactive 376s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s ok 38 /driver/finger_status/waiting 376s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 376s ok 39 /driver/finger_status/present 376s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 376s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 376s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 376s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 376s ok 40 /driver/finger_status/changes 376s # End of finger_status tests 376s # Start of features tests 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 376s # 376s # libfprint-device-DEBUG: Device reported probe completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 41 /driver/features/probe_updates 376s # End of features tests 376s # Start of initial_features tests 376s ok 42 /driver/initial_features/none 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s ok 43 /driver/initial_features/no_capture 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s ok 44 /driver/initial_features/no_verify 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s ok 45 /driver/initial_features/no_identify 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s ok 46 /driver/initial_features/no_storage 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s ok 47 /driver/initial_features/no_list 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s ok 48 /driver/initial_features/no_delete 376s ok 49 /driver/initial_features/no_clear 376s # End of initial_features tests 376s # Start of probe tests 376s # libfprint-device-DEBUG: Device reported probe completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 50 /driver/probe/error 376s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 376s # libfprint-device-DEBUG: Device reported probe completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 51 /driver/probe/action_error 376s # End of probe tests 376s # Start of open tests 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 52 /driver/open/error 376s # End of open tests 376s # Start of close tests 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 53 /driver/close/error 376s # End of close tests 376s # Start of enroll tests 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 376s # 376s # libfprint-device-DEBUG: Device reported enroll completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 54 /driver/enroll/error 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Device reported enroll progress, reported 1251812905 of 70001004 have been completed 376s # libfprint-device-DEBUG: Device reported enroll progress, reported 83319105 of 70001004 have been completed 376s # libfprint-device-DEBUG: Device reported enroll progress, reported 538184784 of 70001004 have been completed 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 376s # 376s # libfprint-device-DEBUG: Device reported enroll completion 376s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 55 /driver/enroll/progress 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 376s # 376s # libfprint-device-DEBUG: Device reported enroll completion 376s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 56 /driver/enroll/update_nbis 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 57 /driver/enroll/update_nbis_wrong_device 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 58 /driver/enroll/update_nbis_wrong_driver 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 59 /driver/enroll/update_nbis_missing_feature 376s # Start of error tests 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Device reported enroll completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Device reported enroll completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Device reported enroll completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 60 /driver/enroll/error/no_print 376s # End of error tests 376s # End of enroll tests 376s # Start of verify tests 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 376s # 376s # libfprint-device-DEBUG: Device reported verify result 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 61 /driver/verify/fail 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 376s # 376s # libfprint-device-DEBUG: Device reported verify result 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 62 /driver/verify/retry 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 376s # 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 63 /driver/verify/error 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 64 /driver/verify/not_supported 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Device reported verify result 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 65 /driver/verify/report_no_cb 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 66 /driver/verify/not_reported 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Device reported verify result 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Device reported verify result 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Device reported verify result 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Device reported verify result 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Device reported verify result 376s # libfprint-device-DEBUG: Device reported verify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 67 /driver/verify/complete_retry 376s # End of verify tests 376s # Start of identify tests 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 376s # 376s # libfprint-device-DEBUG: Device reported identify result 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 68 /driver/identify/fail 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 376s # 376s # libfprint-device-DEBUG: Device reported identify result 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 376s ok 69 /driver/identify/retry 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 376s # 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 376s ok 70 /driver/identify/error 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 376s ok 71 /driver/identify/not_reported 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Device reported identify result 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Device reported identify result 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-device-DEBUG: Device reported identify result 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 72 /driver/identify/complete_retry 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Device reported identify result 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 73 /driver/identify/report_no_cb 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 376s # 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 376s # 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 376s # 376s # libfprint-device-DEBUG: Device reported identify result 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 74 /driver/identify/suspend_continues 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 376s # 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 376s # 376s # libfprint-device-DEBUG: Device reported identify result 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 75 /driver/identify/suspend_succeeds 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 376s # 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 376s # 376s # libfprint-device-DEBUG: Device reported identify completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 376s ok 76 /driver/identify/suspend_busy_error 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 376s # 376s # libfprint-device-DEBUG: Device reported close completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s ok 77 /driver/identify/suspend_while_idle 376s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 376s # libfprint-device-DEBUG: Tod version info is 'current' 376s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 376s # 376s # libfprint-device-DEBUG: Device reported open completion 376s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 376s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 377s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 378s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 378s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 378s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 378s # 378s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 378s # 378s # libfprint-device-DEBUG: Device reported identify completion 378s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 378s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 378s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 378s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 381s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 382s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 384s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 78 /driver/identify/warmup_cooldown 384s # slow test /driver/identify/warmup_cooldown executed in 7.30 secs 384s # End of identify tests 384s # Start of capture tests 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 384s # 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 79 /driver/capture/not_supported 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 384s # 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 384s # 384s # libfprint-device-DEBUG: Device reported capture completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s ok 80 /driver/capture/error 384s # End of capture tests 384s # Start of list tests 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 384s # 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 384s # 384s # libfprint-device-DEBUG: Device reported listing completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 81 /driver/list/error 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 384s # 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 82 /driver/list/no_storage 384s # End of list tests 384s # Start of delete tests 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 384s # 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 384s # 384s # libfprint-device-DEBUG: Device reported deletion completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 83 /driver/delete/error 384s # End of delete tests 384s # Start of clear_storage tests 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 384s # 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 384s # libfprint-device-DEBUG: Tod version info is 'current' 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 384s # 384s # libfprint-device-DEBUG: Device reported deletion completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 84 /driver/clear_storage/error 384s # End of clear_storage tests 384s # Start of cancel tests 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 384s # 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 384s # 384s # libfprint-device-DEBUG: Device reported deletion completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 85 /driver/cancel/fail 384s # End of cancel tests 384s # Start of get_current_action tests 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 86 /driver/get_current_action/open 384s # End of get_current_action tests 384s # Start of get_cancellable tests 384s ok 87 /driver/get_cancellable/error 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 88 /driver/get_cancellable/open 384s # Start of open tests 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 89 /driver/get_cancellable/open/internal 384s # End of open tests 384s # End of get_cancellable tests 384s # Start of action_is_cancelled tests 384s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 384s # libfprint-device-DEBUG: Tod version info is 'current' 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 90 /driver/action_is_cancelled/open 384s ok 91 /driver/action_is_cancelled/error 384s # Start of open tests 384s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 384s # libfprint-device-DEBUG: Tod version info is 'current' 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s ok 92 /driver/action_is_cancelled/open/internal 384s # End of open tests 384s # End of action_is_cancelled tests 384s # Start of complete_action tests 384s # Start of all tests 384s ok 93 /driver/complete_action/all/error 384s # End of all tests 384s # End of complete_action tests 384s # Start of action_error tests 384s ok 94 /driver/action_error/error 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 384s # 384s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 384s # 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 384s # 384s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 384s # libfprint-device-DEBUG: Device reported enroll completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 384s # 384s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 384s # libfprint-device-DEBUG: Device reported verify completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 384s # 384s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 384s # libfprint-device-DEBUG: Device reported identify completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 384s # 384s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 384s # libfprint-device-DEBUG: Device reported capture completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 384s # 384s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 384s # libfprint-device-DEBUG: Device reported listing completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 384s # 384s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 384s # libfprint-device-DEBUG: Device reported deletion completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 384s # libfprint-device-DEBUG: Tod version info is 'current' 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 384s # 384s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 384s # libfprint-device-DEBUG: Device reported deletion completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s ok 95 /driver/action_error/all 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 384s # 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 384s # 384s # libfprint-device-DEBUG: Device reported open completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 384s # 384s # libfprint-device-DEBUG: Device reported enroll completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 384s # 384s # libfprint-device-DEBUG: Device reported verify completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 384s # 384s # libfprint-device-DEBUG: Device reported identify completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 384s # 384s # libfprint-device-DEBUG: Device reported capture completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 384s # 384s # libfprint-device-DEBUG: Device reported listing completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 384s # 384s # libfprint-device-DEBUG: Device reported deletion completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 384s # libfprint-device-DEBUG: Tod version info is 'current' 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 384s # 384s # libfprint-device-DEBUG: Device reported deletion completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 384s # 384s # libfprint-device-DEBUG: Device reported close completion 384s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 384s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 384s ok 96 /driver/action_error/fail 384s # End of action_error tests 384s # Start of timeout tests 384s ok 97 /driver/timeout/cancelled 384s # End of timeout tests 384s # End of driver tests 384s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 384s Running test: libfprint-2/driver-elan.test 384s ** (umockdev-run:1947): DEBUG: 05:08:24.196: umockdev.vala:127: Created udev test bed /tmp/umockdev.4W0F22 384s ** (umockdev-run:1947): DEBUG: 05:08:24.196: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 384s ** (umockdev-run:1947): DEBUG: 05:08:24.199: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 (subsystem usb) 384s ** (umockdev-run:1947): DEBUG: 05:08:24.204: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4W0F22/dev/bus/usb/001/094 384s ** (umockdev-run:1947): DEBUG: 05:08:24.205: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4 384s ** (umockdev-run:1947): DEBUG: 05:08:24.206: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4 (subsystem usb) 384s ** (umockdev-run:1947): DEBUG: 05:08:24.213: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4W0F22/dev/bus/usb/001/083 384s ** (umockdev-run:1947): DEBUG: 05:08:24.213: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 384s ** (umockdev-run:1947): DEBUG: 05:08:24.215: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 384s ** (umockdev-run:1947): DEBUG: 05:08:24.220: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4W0F22/dev/bus/usb/001/001 384s ** (umockdev-run:1947): DEBUG: 05:08:24.220: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 384s ** (umockdev-run:1947): DEBUG: 05:08:24.221: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 384s (umockdev-run:1947): GLib-GIO-DEBUG: 05:08:24.226: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 384s (process:1951): libfprint-context-DEBUG: 05:08:24.349: Initializing FpContext (libfprint version 1.94.9+tod1) 384s (process:1951): libfprint-tod-DEBUG: 05:08:24.349: 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:1951): libfprint-context-DEBUG: 05:08:24.353: No driver found for USB device 17EF:1018 384s (process:1951): libfprint-context-DEBUG: 05:08:24.353: No driver found for USB device 1D6B:0002 384s (process:1951): libfprint-device-DEBUG: 05:08:24.354: Device reported probe completion 384s (process:1951): libfprint-device-DEBUG: 05:08:24.354: Completing action FPI_DEVICE_ACTION_PROBE in idle! 384s (process:1951): libfprint-device-DEBUG: 05:08:24.354: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.356: 130963350289: ../libfprint/drivers/elan.c:908 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.356: Image device open completed 384s (process:1951): libfprint-device-DEBUG: 05:08:24.357: Device reported open completion 384s (process:1951): libfprint-device-DEBUG: 05:08:24.357: Completing action FPI_DEVICE_ACTION_OPEN in idle! 384s (process:1951): libfprint-device-DEBUG: 05:08:24.357: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s (process:1951): libfprint-device-DEBUG: 05:08:24.357: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.357: Activating image device 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.357: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.357: 130963351129: ../libfprint/drivers/elan.c:960 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.357: 130963351138: ../libfprint/drivers/elan.c:951 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.357: 130963351143: ../libfprint/drivers/elan.c:892 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.357: 130963351148: ../libfprint/drivers/elan.c:100 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.357: [elan] ACTIVATE_NUM_STATES entering state 0 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.357: 130963351165: ../libfprint/drivers/elan.c:820 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.358: 130963351857: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.358: 130963351880: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.358: 130963351886: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.359: 130963353100: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.359: 130963353153: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.359: [elan] ACTIVATE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.359: 130963353171: ../libfprint/drivers/elan.c:820 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.359: FW ver 0x0140 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.359: [elan] ACTIVATE_NUM_STATES entering state 2 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.359: 130963353185: ../libfprint/drivers/elan.c:820 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963353797: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963353819: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963353825: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963354554: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963354583: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.360: [elan] ACTIVATE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963354595: ../libfprint/drivers/elan.c:820 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: sensor dimensions, WxH: 144x64 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.360: [elan] ACTIVATE_NUM_STATES entering state 4 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963354607: ../libfprint/drivers/elan.c:820 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963354617: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.360: [elan] ACTIVATE_NUM_STATES completed successfully 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963354626: ../libfprint/drivers/elan.c:881 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.360: Image device activation completed 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963354653: ../libfprint/drivers/elan.c:960 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.360: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963354665: ../libfprint/drivers/elan.c:960 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963354669: ../libfprint/drivers/elan.c:792 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963354674: ../libfprint/drivers/elan.c:100 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.360: [elan] CALIBRATE_NUM_STATES entering state 0 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.360: 130963354683: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-device-DEBUG: 05:08:24.361: Device reported finger status change: FP_FINGER_STATUS_NEEDED 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.361: 130963355271: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.361: 130963355296: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.361: 130963355302: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.362: 130963356136: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.362: 130963356177: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.362: [elan] CALIBRATE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.362: 130963356190: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.362: 130963356195: ../libfprint/drivers/elan.c:156 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.362: 130963356202: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.362: [elan] CALIBRATE_NUM_STATES entering state 2 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.362: 130963356251: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.363: 130963356870: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.363: 130963356888: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.363: 130963356894: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.363: 130963357621: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.363: 130963357647: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.363: [elan] CALIBRATE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.363: 130963357662: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.363: 130963357668: ../libfprint/drivers/elan.c:634 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.363: calibration mean: 8421, bg mean: 5805, delta: 2616 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.363: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.363: 130963357687: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.364: 130963358305: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.364: 130963358330: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.364: 130963358336: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.365: 130963359196: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.365: 130963359234: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.365: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.365: 130963359247: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.365: calibration status: 0x01 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.415: [elan] CALIBRATE_NUM_STATES entering state 6 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.415: 130963409472: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.415: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.415: 130963409499: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.416: 130963410700: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.417: 130963410755: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.417: 130963410764: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.417: 130963411595: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.417: 130963411648: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.417: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.417: 130963411665: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.417: calibration status: 0x01 384s (process:1951): libfprint-device-DEBUG: 05:08:24.457: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.467: [elan] CALIBRATE_NUM_STATES entering state 6 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.468: 130963461740: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.468: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.468: 130963461753: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.469: 130963463047: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.469: 130963463094: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.469: 130963463101: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.470: 130963464247: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.470: 130963464280: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.470: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.470: 130963464296: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.470: calibration status: 0x01 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.520: [elan] CALIBRATE_NUM_STATES entering state 6 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.520: 130963514636: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.520: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.520: 130963514649: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.522: 130963515853: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.522: 130963515901: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.522: 130963515908: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.523: 130963516990: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.523: 130963517045: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.523: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.523: 130963517062: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.523: calibration status: 0x01 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.573: [elan] CALIBRATE_NUM_STATES entering state 6 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.573: 130963567331: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.573: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.573: 130963567406: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.574: 130963568414: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.574: 130963568451: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.574: 130963568458: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.575: 130963569371: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.575: 130963569402: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.575: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.575: 130963569416: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.575: calibration status: 0x01 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.625: [elan] CALIBRATE_NUM_STATES entering state 6 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.625: 130963619550: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.625: [elan] CALIBRATE_NUM_STATES entering state 4 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.625: 130963619563: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.626: 130963620674: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.626: 130963620706: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.626: 130963620713: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.627: 130963621548: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.627: 130963621572: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.627: [elan] CALIBRATE_NUM_STATES entering state 5 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.627: 130963621585: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.627: calibration status: 0x03 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.627: [elan] CALIBRATE_NUM_STATES entering state 0 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.627: 130963621596: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.628: 130963622412: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.628: 130963622435: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.628: 130963622441: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.629: 130963623383: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.629: 130963623406: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.629: [elan] CALIBRATE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.629: 130963623418: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.629: 130963623422: ../libfprint/drivers/elan.c:156 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.629: 130963623426: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.629: [elan] CALIBRATE_NUM_STATES entering state 2 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.629: 130963623444: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.630: 130963624170: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.630: 130963624187: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.630: 130963624193: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.631: 130963624967: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.631: 130963624981: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.631: [elan] CALIBRATE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.631: 130963624991: ../libfprint/drivers/elan.c:691 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.631: 130963624995: ../libfprint/drivers/elan.c:634 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.631: calibration mean: 8339, bg mean: 8146, delta: 193 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.631: [elan] CALIBRATE_NUM_STATES completed successfully 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.631: 130963625056: ../libfprint/drivers/elan.c:776 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.631: 130963625061: ../libfprint/drivers/elan.c:620 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.631: 130963625064: ../libfprint/drivers/elan.c:100 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.631: [elan] CAPTURE_NUM_STATES entering state 0 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.632: 130963625964: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.632: 130963625978: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.632: 130963625985: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.632: skipping read, not expecting anything 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.632: 130963625993: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.632: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.633: 130963626769: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.633: 130963626783: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.633: 130963626789: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.633: 130963627664: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.633: 130963627681: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.633: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-device-DEBUG: 05:08:24.633: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.633: Image device reported finger status: on 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.633: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.634: 130963627723: ../libfprint/drivers/elan.c:960 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.634: 130963628494: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.634: 130963628512: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.634: 130963628518: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.635: 130963629382: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.635: 130963629406: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.635: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.635: 130963629418: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.635: 130963629439: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.635: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.636: 130963630299: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.636: 130963630322: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.636: 130963630328: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.637: 130963631151: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.637: 130963631170: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.637: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.637: Image device reported finger status: on 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.638: 130963631922: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.638: 130963631937: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.638: 130963631942: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.639: 130963632775: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.639: 130963632795: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.639: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.639: 130963632806: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.639: 130963632819: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.639: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.639: 130963633548: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.639: 130963633568: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.639: 130963633574: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.640: 130963634320: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.640: 130963634337: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.640: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.640: Image device reported finger status: on 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.641: 130963635055: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.641: 130963635068: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.641: 130963635074: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.642: 130963636269: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.642: 130963636290: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.642: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.642: 130963636301: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.642: 130963636326: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.642: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.643: 130963637178: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.643: 130963637194: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.643: 130963637201: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.644: 130963637938: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.644: 130963637952: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.644: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.644: Image device reported finger status: on 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.644: 130963638711: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.645: 130963638728: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.645: 130963638735: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.645: 130963639618: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.645: 130963639638: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.645: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.645: 130963639650: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.645: 130963639664: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.645: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.646: 130963640516: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.646: 130963640534: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.646: 130963640541: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.647: 130963641355: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.647: 130963641371: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.647: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.647: Image device reported finger status: on 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.648: 130963642057: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.648: 130963642073: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.648: 130963642079: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.649: 130963642948: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.649: 130963642964: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.649: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.649: 130963642974: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.649: 130963642988: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.649: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.650: 130963643724: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.650: 130963643739: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.650: 130963643745: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.650: 130963644578: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.650: 130963644595: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.650: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.650: Image device reported finger status: on 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.651: 130963645466: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.651: 130963645483: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.651: 130963645490: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.652: 130963646341: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.652: 130963646361: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.652: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.652: 130963646372: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.652: 130963646384: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.652: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.653: 130963646984: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.653: 130963646998: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.653: 130963647019: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.654: 130963647818: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.654: 130963647831: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.654: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.654: Image device reported finger status: on 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.654: 130963648620: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.654: 130963648637: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.654: 130963648645: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.655: 130963649590: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.655: 130963649609: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.655: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.655: 130963649620: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.655: 130963649634: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.655: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.656: 130963650443: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.656: 130963650461: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.656: 130963650467: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.657: 130963651276: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.657: 130963651292: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.657: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.657: Image device reported finger status: on 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.658: 130963651974: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.658: 130963651987: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.658: 130963651993: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.659: 130963652897: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.659: 130963652918: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.659: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.659: 130963652928: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.659: 130963652941: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.659: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.660: 130963653732: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.660: 130963653749: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.660: 130963653757: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.660: 130963654524: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.660: 130963654540: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.660: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.660: Image device reported finger status: on 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.661: 130963655277: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.661: 130963655294: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.661: 130963655299: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.662: 130963656144: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.662: 130963656161: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.662: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.662: 130963656173: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.662: 130963656189: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.662: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.663: 130963656896: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.663: 130963656912: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.663: 130963656917: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.663: 130963657707: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.664: 130963657726: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.664: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.664: Image device reported finger status: on 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.664: 130963658496: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.664: 130963658512: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.664: 130963658518: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.665: 130963659404: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.665: 130963659422: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.665: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.665: 130963659432: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.665: 130963659444: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.665: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.666: 130963660323: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.666: 130963660342: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.666: 130963660348: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.667: 130963661129: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.667: 130963661144: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.667: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.667: Image device reported finger status: on 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.668: 130963661881: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.668: 130963661893: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.668: 130963661898: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.669: 130963662760: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.669: 130963662781: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.669: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.669: 130963662792: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.669: 130963662803: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.669: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.669: 130963663506: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.669: 130963663524: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.669: 130963663530: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.670: 130963664268: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.670: 130963664284: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.670: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-image_device-DEBUG: 05:08:24.670: Image device reported finger status: on 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.671: 130963664950: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.671: 130963664962: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.671: 130963664967: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.672: 130963665878: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.672: 130963665900: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.672: [elan] CAPTURE_NUM_STATES entering state 3 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.672: 130963665910: ../libfprint/drivers/elan.c:203 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.672: 130963665920: ../libfprint/drivers/elan.c:118 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.672: [elan] CAPTURE_NUM_STATES entering state 1 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.672: 130963666640: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.672: 130963666656: ../libfprint/drivers/elan.c:366 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.672: 130963666662: ../libfprint/drivers/elan.c:379 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.673: 130963667379: ../libfprint/drivers/elan.c:346 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.673: 130963667395: ../libfprint/drivers/elan.c:335 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.673: [elan] CAPTURE_NUM_STATES entering state 2 384s (process:1951): libfprint-SSM-DEBUG: 05:08:24.673: [elan] CAPTURE_NUM_STATES completed successfully 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.673: 130963667417: ../libfprint/drivers/elan.c:586 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.673: 130963667420: ../libfprint/drivers/elan.c:315 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.673: 130963667427: ../libfprint/drivers/elan.c:272 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.674: 130963668369: ../libfprint/drivers/elan.c:272 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.675: 130963669250: ../libfprint/drivers/elan.c:272 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.676: 130963670116: ../libfprint/drivers/elan.c:272 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.677: 130963670975: ../libfprint/drivers/elan.c:272 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.678: 130963671864: ../libfprint/drivers/elan.c:272 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.679: 130963672747: ../libfprint/drivers/elan.c:272 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.679: 130963673625: ../libfprint/drivers/elan.c:272 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.680: 130963674501: ../libfprint/drivers/elan.c:272 384s (process:1951): libfprint-elan-DEBUG: 05:08:24.681: 130963675381: ../libfprint/drivers/elan.c:272 384s (process:1951): libfprint-assembling-DEBUG: 05:08:24.860: calc delta completed in 0.177833 secs 385s (process:1951): libfprint-assembling-DEBUG: 05:08:25.037: calc delta completed in 0.176974 secs 385s (process:1951): libfprint-assembling-DEBUG: 05:08:25.037: errors: 233151 rev: 207411 385s (process:1951): libfprint-assembling-DEBUG: 05:08:25.037: height is -185 385s (process:1951): libfprint-image_device-DEBUG: 05:08:25.037: Image device captured an image 385s (process:1951): libfprint-image_device-DEBUG: 05:08:25.040: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.040: 130964033910: ../libfprint/drivers/elan.c:960 385s (process:1951): libfprint-device-DEBUG: 05:08:25.040: Device reported finger status change: FP_FINGER_STATUS_PRESENT 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.040: 130964033930: ../libfprint/drivers/elan.c:507 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.040: 130964033936: ../libfprint/drivers/elan.c:100 385s (process:1951): libfprint-SSM-DEBUG: 05:08:25.040: [elan] STOP_CAPTURE_NUM_STATES entering state 0 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.040: 130964033950: ../libfprint/drivers/elan.c:466 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.041: 130964034798: ../libfprint/drivers/elan.c:346 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.041: 130964034826: ../libfprint/drivers/elan.c:366 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.041: 130964034833: ../libfprint/drivers/elan.c:379 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.041: skipping read, not expecting anything 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.041: 130964034842: ../libfprint/drivers/elan.c:335 385s (process:1951): libfprint-SSM-DEBUG: 05:08:25.041: [elan] STOP_CAPTURE_NUM_STATES completed successfully 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.041: 130964034850: ../libfprint/drivers/elan.c:483 385s (process:1951): libfprint-device-DEBUG: 05:08:25.041: Device reported finger status change: FP_FINGER_STATUS_NONE 385s (process:1951): libfprint-image_device-DEBUG: 05:08:25.041: Image device reported finger status: off 385s (process:1951): libfprint-image_device-DEBUG: 05:08:25.041: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.041: 130964034875: ../libfprint/drivers/elan.c:960 385s (process:1951): libfprint-image_device-DEBUG: 05:08:25.041: Deactivating image device 385s (process:1951): libfprint-image_device-DEBUG: 05:08:25.041: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.041: 130964034888: ../libfprint/drivers/elan.c:960 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.041: 130964034893: ../libfprint/drivers/elan.c:975 385s (process:1951): libfprint-image_device-DEBUG: 05:08:25.041: Image device deactivation completed 385s (process:1951): libfprint-image_device-DEBUG: 05:08:25.041: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.041: 130964034922: ../libfprint/drivers/elan.c:960 385s (process:1951): libfprint-image-DEBUG: 05:08:25.058: Minutiae scan completed in 0.017818 secs 385s (process:1951): libfprint-device-DEBUG: 05:08:25.058: Device reported capture completion 385s (process:1951): libfprint-device-DEBUG: 05:08:25.058: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 385s (process:1951): libfprint-device-DEBUG: 05:08:25.058: Updated temperature model after 0.60 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.059: 130964052914: ../libfprint/drivers/elan.c:939 385s (process:1951): libfprint-elan-DEBUG: 05:08:25.059: 130964053047: ../libfprint/drivers/elan.c:100 385s (process:1951): libfprint-image_device-DEBUG: 05:08:25.059: Image device close completed 385s (process:1951): libfprint-device-DEBUG: 05:08:25.059: Device reported close completion 385s (process:1951): libfprint-device-DEBUG: 05:08:25.059: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 385s (process:1951): libfprint-device-DEBUG: 05:08:25.060: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 385s ** (umockdev-run:1947): DEBUG: 05:08:25.159: umockdev.vala:154: Removing test bed /tmp/umockdev.4W0F22 385s (umockdev-run:1947): GLib-DEBUG: 05:08:25.170: unsetenv() is not thread-safe and should not be used after threads are created 385s Comparing PNGs /tmp/libfprint-umockdev-test-aqrwguvj/capture.png and /usr/share/installed-tests/libfprint-2/elan/capture.png 385s PASS: libfprint-2/driver-elan.test 385s Running test: libfprint-2/fp-context.test 385s TAP version 14 385s # random seed: R02S3fa7abe2c0be64bfd11a8819b351676b 385s 1..9 385s # Start of context tests 385s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 385s # 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 385s ok 1 /context/new 385s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 385s # 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 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 385s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 385s ok 2 /context/no-devices 385s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 385s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 385s # 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 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 385s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 385s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ZA3E22/virtual_image.socket 385s # libfprint-context-DEBUG: created 385s # libfprint-device-DEBUG: Device reported probe completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 385s ok 3 /context/has-virtual-device 385s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 385s # 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 385s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 385s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 385s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-IILE22/virtual_image.socket 385s # libfprint-context-DEBUG: created 385s # libfprint-device-DEBUG: Device reported probe completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 385s ok 4 /context/enumerates-new-devices 385s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 385s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 385s # 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 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 385s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 385s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-70JE22/virtual_image.socket 385s # libfprint-context-DEBUG: created 385s # libfprint-device-DEBUG: Device reported probe completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 385s ok 5 /context/remove-device-closed 385s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 385s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 385s # 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 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 385s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 385s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-IWGE22/virtual_image.socket 385s # libfprint-context-DEBUG: created 385s # libfprint-device-DEBUG: Device reported probe completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_image-DEBUG: 05:08:25.256: 130964249833: ../libfprint/drivers/virtual-image.c:216 385s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_device_connection-DEBUG: 05:08:25.256: 130964249949: ../libfprint/drivers/virtual-device-listener.c:153 385s # libfprint-image_device-DEBUG: Image device open completed 385s # libfprint-device-DEBUG: Device reported open completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_image-DEBUG: 05:08:25.357: 130964350758: ../libfprint/drivers/virtual-image.c:244 385s # libfprint-image_device-DEBUG: Image device close completed 385s # libfprint-device-DEBUG: Device reported close completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 385s ok 6 /context/remove-device-closing 385s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 385s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 385s # 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 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 385s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 385s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-Z0NL22/virtual_image.socket 385s # libfprint-context-DEBUG: created 385s # libfprint-device-DEBUG: Device reported probe completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_image-DEBUG: 05:08:25.461: 130964455125: ../libfprint/drivers/virtual-image.c:216 385s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_device_connection-DEBUG: 05:08:25.461: 130964455152: ../libfprint/drivers/virtual-device-listener.c:153 385s # libfprint-image_device-DEBUG: Image device open completed 385s # libfprint-device-DEBUG: Device reported open completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_image-DEBUG: 05:08:25.562: 130964555942: ../libfprint/drivers/virtual-image.c:244 385s # libfprint-image_device-DEBUG: Image device close completed 385s # libfprint-device-DEBUG: Device reported close completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 385s ok 7 /context/remove-device-open 385s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 385s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 385s # 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 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 385s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 385s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-V49312/virtual_image.socket 385s # libfprint-context-DEBUG: created 385s # libfprint-device-DEBUG: Device reported probe completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_image-DEBUG: 05:08:25.666: 130964659888: ../libfprint/drivers/virtual-image.c:216 385s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_device_connection-DEBUG: 05:08:25.666: 130964659913: ../libfprint/drivers/virtual-device-listener.c:153 385s # libfprint-image_device-DEBUG: Image device open completed 385s # libfprint-device-DEBUG: Device reported open completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_image-DEBUG: 05:08:25.766: 130964760469: ../libfprint/drivers/virtual-image.c:244 385s # libfprint-image_device-DEBUG: Image device close completed 385s # libfprint-device-DEBUG: Device reported close completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 385s ok 8 /context/remove-device-opening 385s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 385s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 385s # 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 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 385s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 385s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 385s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-C9U512/virtual_image.socket 385s # libfprint-context-DEBUG: created 385s # libfprint-device-DEBUG: Device reported probe completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_image-DEBUG: 05:08:25.870: 130964864182: ../libfprint/drivers/virtual-image.c:216 385s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_device_connection-DEBUG: 05:08:25.870: 130964864206: ../libfprint/drivers/virtual-device-listener.c:153 385s # libfprint-image_device-DEBUG: Image device open completed 385s # libfprint-device-DEBUG: Device reported open completion 385s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 385s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 385s # libfprint-image_device-DEBUG: Activating image device 385s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 385s # libfprint-image_device-DEBUG: Image device activation completed 385s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 385s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 385s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 386s # libfprint-image_device-DEBUG: Deactivating image device 386s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 386s # libfprint-image_device-DEBUG: Image device deactivation completed 386s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 386s # libfprint-device-DEBUG: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL 386s # libfprint-device-DEBUG: Device reported enroll completion 386s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 386s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 386s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:1958): libfprint-virtual_image-DEBUG: 05:08:25.971: 130964965244: ../libfprint/drivers/virtual-image.c:244 386s # libfprint-image_device-DEBUG: Image device close completed 386s # libfprint-device-DEBUG: Device reported close completion 386s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 386s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 386s ok 9 /context/remove-device-active 386s # End of context tests 386s PASS: libfprint-2/fp-context.test 386s Running test: libfprint-2/virtual-device.test 386s (process:1980): libfprint-context-DEBUG: 05:08:26.209: Initializing FpContext (libfprint version 1.94.9+tod1) 386s (process:1980): libfprint-tod-DEBUG: 05:08:26.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 386s (process:1980): libfprint-context-DEBUG: 05:08:26.212: No driver found for USB device 1D6B:0003 386s (process:1980): libfprint-context-DEBUG: 05:08:26.212: No driver found for USB device 0627:0001 386s (process:1980): libfprint-context-DEBUG: 05:08:26.212: No driver found for USB device 1D6B:0002 386s (process:1980): libfprint-context-DEBUG: 05:08:26.212: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-nsyc4f4q/virtual-device.socket 386s (process:1980): libfprint-context-DEBUG: 05:08:26.213: created 386s (process:1980): libfprint-device-DEBUG: 05:08:26.214: Device reported probe completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.214: Completing action FPI_DEVICE_ACTION_PROBE in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.214: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s test_capture_unsupported (__main__.VirtualDevice.test_capture_unsupported) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.214: 130965208648: ../libfprint/drivers/virtual-device.c:387 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.215: 130965208751: ../libfprint/drivers/virtual-device-listener.c:153 386s (process:1980): libfprint-device-DEBUG: 05:08:26.215: Device reported open completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.215: Completing action FPI_DEVICE_ACTION_OPEN in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.215: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.216: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.216: Got instructions of length 16 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.216: Received command SET_KEEP_ALIVE 0 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.216: Keep alive toggled: 0 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.216: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.216: Got instructions of length 19 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.216: Received command SET_ENROLL_STAGES 5 386s (process:1980): libfprint-device-DEBUG: 05:08:26.216: Device reported close completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.216: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.216: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s ok 386s test_change_enroll_stages (__main__.VirtualDevice.test_change_enroll_stages) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.216: 130965210697: ../libfprint/drivers/virtual-device.c:387 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.216: 130965210718: ../libfprint/drivers/virtual-device-listener.c:153 386s (process:1980): libfprint-device-DEBUG: 05:08:26.217: Device reported open completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.217: Completing action FPI_DEVICE_ACTION_OPEN in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.217: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.217: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.217: Got instructions of length 20 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.217: Received command SET_ENROLL_STAGES 20 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.218: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.218: Got instructions of length 19 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.218: Received command SET_ENROLL_STAGES 1 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.218: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.218: Got instructions of length 19 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.218: Received command SET_ENROLL_STAGES 0 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.220: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.220: Got instructions of length 16 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.220: Received command SET_KEEP_ALIVE 0 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.220: Keep alive toggled: 0 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.220: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.220: Got instructions of length 19 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.220: Received command SET_ENROLL_STAGES 5 386s (process:1980): libfprint-device-DEBUG: 05:08:26.220: Device reported close completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.220: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.220: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s ok 386s test_change_scan_type (__main__.VirtualDevice.test_change_scan_type) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.221: 130965214731: ../libfprint/drivers/virtual-device.c:387 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.221: 130965214744: ../libfprint/drivers/virtual-device-listener.c:153 386s (process:1980): libfprint-device-DEBUG: 05:08:26.221: Device reported open completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.221: Completing action FPI_DEVICE_ACTION_OPEN in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.221: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.221: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.221: Got instructions of length 19 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.221: Received command SET_SCAN_TYPE press 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.222: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.222: Got instructions of length 19 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.222: Received command SET_SCAN_TYPE swipe 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.222: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.222: Got instructions of length 25 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.222: Received command SET_SCAN_TYPE eye-contact 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.222: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.222: Got instructions of length 16 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.222: Received command SET_KEEP_ALIVE 0 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.222: Keep alive toggled: 0 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.223: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.223: Got instructions of length 19 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.223: Received command SET_ENROLL_STAGES 5 386s (process:1980): libfprint-device-DEBUG: 05:08:26.223: Device reported close completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.223: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.223: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s ok 386s test_close_error (__main__.VirtualDevice.test_close_error) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.223: 130965217130: ../libfprint/drivers/virtual-device.c:387 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.223: 130965217144: ../libfprint/drivers/virtual-device-listener.c:153 386s (process:1980): libfprint-device-DEBUG: 05:08:26.223: Device reported open completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.223: Completing action FPI_DEVICE_ACTION_OPEN in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.223: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.223: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.223: Got instructions of length 9 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.223: Received command SLEEP 100 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.224: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.224: Got instructions of length 7 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.224: Received command ERROR 4 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.224: Processing command SLEEP 100 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.224: Sleeping 100ms 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.325: Sleeping completed 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.325: Processing command ERROR 4 386s (process:1980): libfprint-device-DEBUG: 05:08:26.325: Device reported close completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.325: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.325: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s ok 386s test_close_while_opening (__main__.VirtualDevice.test_close_while_opening) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.325: 130965319681: ../libfprint/drivers/virtual-device.c:387 386s (process:1980): libfprint-device-DEBUG: 05:08:26.325: Device reported open completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.326: Completing action FPI_DEVICE_ACTION_OPEN in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.326: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.326: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.326: Got instructions of length 16 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.326: Received command SET_KEEP_ALIVE 1 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.326: Keep alive toggled: 1 386s (process:1980): libfprint-device-DEBUG: 05:08:26.326: Device reported close completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.326: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.326: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.326: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.326: Got instructions of length 9 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.326: Received command SLEEP 500 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.327: 130965320791: ../libfprint/drivers/virtual-device.c:387 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.327: Processing command SLEEP 500 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.327: Sleeping 500ms 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.827: Sleeping completed 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.827: 130965821484: ../libfprint/drivers/virtual-device.c:387 386s (process:1980): libfprint-device-DEBUG: 05:08:26.827: Device reported open completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.827: Completing action FPI_DEVICE_ACTION_OPEN in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.827: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.828: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.828: Got instructions of length 16 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.828: Received command SET_KEEP_ALIVE 0 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.828: Keep alive toggled: 0 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.828: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.828: Got instructions of length 19 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.828: Received command SET_ENROLL_STAGES 5 386s (process:1980): libfprint-device-DEBUG: 05:08:26.828: Device reported close completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.828: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.829: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s ok 386s test_delayed_open (__main__.VirtualDevice.test_delayed_open) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.829: 130965822857: ../libfprint/drivers/virtual-device.c:387 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.829: 130965822883: ../libfprint/drivers/virtual-device-listener.c:153 386s (process:1980): libfprint-device-DEBUG: 05:08:26.829: Device reported open completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.829: Completing action FPI_DEVICE_ACTION_OPEN in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.829: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.829: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.829: Got instructions of length 16 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.829: Received command IGNORED_COMMAND 386s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:26.829: Got a new connection! 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.830: Got instructions of length 9 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.830: Received command SLEEP 500 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.830: Processing command IGNORED_COMMAND 386s (process:1980): libfprint-device-DEBUG: 05:08:26.830: Device reported close completion 386s (process:1980): libfprint-device-DEBUG: 05:08:26.830: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 386s (process:1980): libfprint-device-DEBUG: 05:08:26.830: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.830: 130965824445: ../libfprint/drivers/virtual-device.c:387 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.830: Processing command SLEEP 500 386s (process:1980): libfprint-virtual_device-DEBUG: 05:08:26.830: Sleeping 500ms 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.331: Sleeping completed 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.331: 130966325159: ../libfprint/drivers/virtual-device.c:387 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.331: 130966325179: ../libfprint/drivers/virtual-device-listener.c:153 387s (process:1980): libfprint-device-DEBUG: 05:08:27.331: Device reported open completion 387s (process:1980): libfprint-device-DEBUG: 05:08:27.331: Completing action FPI_DEVICE_ACTION_OPEN in idle! 387s (process:1980): libfprint-device-DEBUG: 05:08:27.331: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.332: Got a new connection! 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.332: Got instructions of length 16 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.332: Received command SET_KEEP_ALIVE 0 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.332: Keep alive toggled: 0 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.332: Got a new connection! 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.332: Got instructions of length 19 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.332: Received command SET_ENROLL_STAGES 5 387s (process:1980): libfprint-device-DEBUG: 05:08:27.332: Device reported close completion 387s (process:1980): libfprint-device-DEBUG: 05:08:27.332: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 387s (process:1980): libfprint-device-DEBUG: 05:08:27.332: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s ok 387s test_delayed_open_with_keep_alive (__main__.VirtualDevice.test_delayed_open_with_keep_alive) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.332: 130966326487: ../libfprint/drivers/virtual-device.c:387 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.332: 130966326500: ../libfprint/drivers/virtual-device-listener.c:153 387s (process:1980): libfprint-device-DEBUG: 05:08:27.332: Device reported open completion 387s (process:1980): libfprint-device-DEBUG: 05:08:27.333: Completing action FPI_DEVICE_ACTION_OPEN in idle! 387s (process:1980): libfprint-device-DEBUG: 05:08:27.333: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.333: Got a new connection! 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.333: Got instructions of length 16 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.333: Received command SET_KEEP_ALIVE 1 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.333: Keep alive toggled: 1 387s (process:1980): libfprint-device-DEBUG: 05:08:27.333: Device reported close completion 387s (process:1980): libfprint-device-DEBUG: 05:08:27.333: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 387s (process:1980): libfprint-device-DEBUG: 05:08:27.333: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.333: Got a new connection! 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.333: Got instructions of length 9 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.333: Received command SLEEP 500 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.333: 130966327437: ../libfprint/drivers/virtual-device.c:387 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.333: Processing command SLEEP 500 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.333: Sleeping 500ms 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.834: Sleeping completed 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.834: 130966828173: ../libfprint/drivers/virtual-device.c:387 387s (process:1980): libfprint-device-DEBUG: 05:08:27.834: Device reported open completion 387s (process:1980): libfprint-device-DEBUG: 05:08:27.834: Completing action FPI_DEVICE_ACTION_OPEN in idle! 387s (process:1980): libfprint-device-DEBUG: 05:08:27.834: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.834: Got a new connection! 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.835: Got instructions of length 16 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.835: Received command SET_KEEP_ALIVE 0 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.835: Keep alive toggled: 0 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.835: Got a new connection! 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.835: Got instructions of length 19 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.835: Received command SET_ENROLL_STAGES 5 387s (process:1980): libfprint-device-DEBUG: 05:08:27.835: Device reported close completion 387s (process:1980): libfprint-device-DEBUG: 05:08:27.835: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 387s (process:1980): libfprint-device-DEBUG: 05:08:27.835: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s ok 387s test_device_features (__main__.VirtualDevice.test_device_features) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.835: 130966829647: ../libfprint/drivers/virtual-device.c:387 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.835: 130966829666: ../libfprint/drivers/virtual-device-listener.c:153 387s (process:1980): libfprint-device-DEBUG: 05:08:27.836: Device reported open completion 387s (process:1980): libfprint-device-DEBUG: 05:08:27.836: Completing action FPI_DEVICE_ACTION_OPEN in idle! 387s (process:1980): libfprint-device-DEBUG: 05:08:27.836: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.836: Got a new connection! 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.836: Got instructions of length 16 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.836: Received command SET_KEEP_ALIVE 0 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.836: Keep alive toggled: 0 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.836: Got a new connection! 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.836: Got instructions of length 19 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.836: Received command SET_ENROLL_STAGES 5 387s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:463: DeprecationWarning: FPrint.Device.supports_identify is deprecated 387s self.assertFalse(self.dev.supports_identify()) 387s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:464: DeprecationWarning: FPrint.Device.supports_capture is deprecated 387s self.assertFalse(self.dev.supports_capture()) 387s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:465: DeprecationWarning: FPrint.Device.has_storage is deprecated 387s self.assertFalse(self.dev.has_storage()) 387s (process:1980): libfprint-device-DEBUG: 05:08:27.837: Device reported close completion 387s (process:1980): libfprint-device-DEBUG: 05:08:27.837: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 387s (process:1980): libfprint-device-DEBUG: 05:08:27.837: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s ok 387s test_device_properties (__main__.VirtualDevice.test_device_properties) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.837: 130966830951: ../libfprint/drivers/virtual-device.c:387 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.837: 130966830967: ../libfprint/drivers/virtual-device-listener.c:153 387s (process:1980): libfprint-device-DEBUG: 05:08:27.837: Device reported open completion 387s (process:1980): libfprint-device-DEBUG: 05:08:27.837: Completing action FPI_DEVICE_ACTION_OPEN in idle! 387s (process:1980): libfprint-device-DEBUG: 05:08:27.837: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.837: Got a new connection! 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.838: Got instructions of length 16 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.838: Received command SET_KEEP_ALIVE 0 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.838: Keep alive toggled: 0 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.838: Got a new connection! 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.838: Got instructions of length 19 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.838: Received command SET_ENROLL_STAGES 5 387s (process:1980): libfprint-device-DEBUG: 05:08:27.838: Device reported close completion 387s (process:1980): libfprint-device-DEBUG: 05:08:27.838: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 387s (process:1980): libfprint-device-DEBUG: 05:08:27.838: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s ok 387s test_device_sleep (__main__.VirtualDevice.test_device_sleep) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.838: 130966832213: ../libfprint/drivers/virtual-device.c:387 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.838: 130966832252: ../libfprint/drivers/virtual-device-listener.c:153 387s (process:1980): libfprint-device-DEBUG: 05:08:27.838: Device reported open completion 387s (process:1980): libfprint-device-DEBUG: 05:08:27.838: Completing action FPI_DEVICE_ACTION_OPEN in idle! 387s (process:1980): libfprint-device-DEBUG: 05:08:27.838: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:27.838: Got a new connection! 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.838: Got instructions of length 10 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.838: Received command SLEEP 1500 387s (process:1980): libfprint-device-DEBUG: 05:08:27.839: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.839: Processing command SLEEP 1500 387s (process:1980): libfprint-virtual_device-DEBUG: 05:08:27.839: Sleeping 1500ms 387s Executing: libfprint-2/virtual-device.test 388s (process:1980): libfprint-device-DEBUG: 05:08:28.138: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 388s (process:1980): libfprint-device-DEBUG: 05:08:28.139: Idle cancelling on ongoing operation! 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.139: Got cancellation! 388s (process:1980): libfprint-device-DEBUG: 05:08:28.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.140: Virtual device scan failed with error: Operation was cancelled 388s (process:1980): libfprint-device-DEBUG: 05:08:28.140: Device reported verify completion 388s (process:1980): libfprint-device-DEBUG: 05:08:28.140: Device reported finger status change: FP_FINGER_STATUS_NONE 388s (process:1980): libfprint-device-DEBUG: 05:08:28.140: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 388s (process:1980): libfprint-device-DEBUG: 05:08:28.140: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:28.340: Got a new connection! 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.340: Got instructions of length 16 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.340: Received command SET_KEEP_ALIVE 0 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.340: Keep alive toggled: 0 388s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:28.340: Got a new connection! 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.340: Got instructions of length 19 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.340: Received command SET_ENROLL_STAGES 5 388s (process:1980): libfprint-device-DEBUG: 05:08:28.340: Device reported close completion 388s (process:1980): libfprint-device-DEBUG: 05:08:28.340: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 388s (process:1980): libfprint-device-DEBUG: 05:08:28.340: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s ok 388s test_device_sleep_before_completing_verify (__main__.VirtualDevice.test_device_sleep_before_completing_verify) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.341: 130967334802: ../libfprint/drivers/virtual-device.c:387 388s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:28.341: 130967334827: ../libfprint/drivers/virtual-device-listener.c:153 388s (process:1980): libfprint-device-DEBUG: 05:08:28.341: Device reported open completion 388s (process:1980): libfprint-device-DEBUG: 05:08:28.341: Completing action FPI_DEVICE_ACTION_OPEN in idle! 388s (process:1980): libfprint-device-DEBUG: 05:08:28.341: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:28.341: Got a new connection! 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.341: Got instructions of length 14 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.341: Received command SCAN foo-print 388s (process:1980): libfprint-device-DEBUG: 05:08:28.342: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.342: Processing command SCAN foo-print 388s (process:1980): libfprint-device-DEBUG: 05:08:28.342: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1980): libfprint-device-DEBUG: 05:08:28.342: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1980): libfprint-device-DEBUG: 05:08:28.342: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1980): libfprint-device-DEBUG: 05:08:28.342: Device reported enroll progress, reported 1 of 5 have been completed 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.342: Sleeping completed 388s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:28.342: Got a new connection! 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.342: Got instructions of length 14 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.342: Received command SCAN foo-print 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.342: Processing command SCAN foo-print 388s (process:1980): libfprint-device-DEBUG: 05:08:28.342: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1980): libfprint-device-DEBUG: 05:08:28.342: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1980): libfprint-device-DEBUG: 05:08:28.342: Device reported enroll progress, reported 2 of 5 have been completed 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.342: Sleeping completed 388s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:28.343: Got a new connection! 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.343: Got instructions of length 14 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.343: Received command SCAN foo-print 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.343: Processing command SCAN foo-print 388s (process:1980): libfprint-device-DEBUG: 05:08:28.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1980): libfprint-device-DEBUG: 05:08:28.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1980): libfprint-device-DEBUG: 05:08:28.343: Device reported enroll progress, reported 3 of 5 have been completed 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.343: Sleeping completed 388s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:28.343: Got a new connection! 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.343: Got instructions of length 14 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.343: Received command SCAN foo-print 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.343: Processing command SCAN foo-print 388s (process:1980): libfprint-device-DEBUG: 05:08:28.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1980): libfprint-device-DEBUG: 05:08:28.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1980): libfprint-device-DEBUG: 05:08:28.343: Device reported enroll progress, reported 4 of 5 have been completed 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.343: Sleeping completed 388s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:28.344: Got a new connection! 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.344: Got instructions of length 14 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.344: Received command SCAN foo-print 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.344: Processing command SCAN foo-print 388s (process:1980): libfprint-device-DEBUG: 05:08:28.344: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1980): libfprint-device-DEBUG: 05:08:28.344: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1980): libfprint-device-DEBUG: 05:08:28.344: Device reported enroll progress, reported 5 of 5 have been completed 388s (process:1980): libfprint-device-DEBUG: 05:08:28.344: Device reported enroll completion 388s (process:1980): libfprint-device-DEBUG: 05:08:28.344: Device reported finger status change: FP_FINGER_STATUS_NONE 388s (process:1980): libfprint-device-DEBUG: 05:08:28.344: Print for finger FP_FINGER_LEFT_RING enrolled 388s (process:1980): libfprint-device-DEBUG: 05:08:28.344: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 388s (process:1980): libfprint-device-DEBUG: 05:08:28.344: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:28.345: Got a new connection! 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.345: Got instructions of length 9 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.345: Received command SLEEP 100 388s (process:1980): libfprint-device-DEBUG: 05:08:28.345: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.345: Processing command SLEEP 100 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.345: Sleeping 100ms 388s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:28.345: Got a new connection! 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.345: Got instructions of length 14 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.345: Received command SCAN bar-print 388s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:28.345: Got a new connection! 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.345: Got instructions of length 9 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.345: Received command SLEEP 800 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.445: Sleeping completed 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.445: Processing command SCAN bar-print 388s (process:1980): libfprint-device-DEBUG: 05:08:28.445: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1980): libfprint-device-DEBUG: 05:08:28.445: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.445: Virtual device scanned print bar-print 388s (process:1980): libfprint-device-DEBUG: 05:08:28.445: Device reported verify result 388s (process:1980): libfprint-device-DEBUG: 05:08:28.445: Device reported finger status change: FP_FINGER_STATUS_NEEDED 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.445: Processing command SLEEP 800 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.445: Sleeping 800ms 388s (process:1980): libfprint-virtual_device-DEBUG: 05:08:28.445: Sleeping now, command queued for later: SCAN bar-print 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.246: Sleeping completed 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.246: Processing command SCAN bar-print 389s (process:1980): libfprint-device-DEBUG: 05:08:29.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.246: Virtual device scanned print bar-print 389s (process:1980): libfprint-device-DEBUG: 05:08:29.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED 389s (process:1980): libfprint-device-DEBUG: 05:08:29.246: Device reported verify completion 389s (process:1980): libfprint-device-DEBUG: 05:08:29.246: Device reported finger status change: FP_FINGER_STATUS_NONE 389s (process:1980): libfprint-device-DEBUG: 05:08:29.247: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 389s (process:1980): libfprint-device-DEBUG: 05:08:29.247: Updated temperature model after 0.90 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 389s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:29.247: Got a new connection! 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.247: Got instructions of length 16 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.247: Received command SET_KEEP_ALIVE 0 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.247: Keep alive toggled: 0 389s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:29.247: Got a new connection! 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.247: Got instructions of length 19 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.247: Received command SET_ENROLL_STAGES 5 389s (process:1980): libfprint-device-DEBUG: 05:08:29.247: Device reported close completion 389s (process:1980): libfprint-device-DEBUG: 05:08:29.248: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 389s (process:1980): libfprint-device-DEBUG: 05:08:29.248: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 389s Enroll done 389s ok 389s test_device_sleep_on_cancellation (__main__.VirtualDevice.test_device_sleep_on_cancellation) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.248: 130968241882: ../libfprint/drivers/virtual-device.c:387 389s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:29.248: 130968241895: ../libfprint/drivers/virtual-device-listener.c:153 389s (process:1980): libfprint-device-DEBUG: 05:08:29.248: Device reported open completion 389s (process:1980): libfprint-device-DEBUG: 05:08:29.248: Completing action FPI_DEVICE_ACTION_OPEN in idle! 389s (process:1980): libfprint-device-DEBUG: 05:08:29.248: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 389s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:29.248: Got a new connection! 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.248: Got instructions of length 26 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.248: Received command SET_CANCELLATION_ENABLED 0 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.248: Cancellation support toggled: 0 389s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:29.248: Got a new connection! 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.249: Got instructions of length 10 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.249: Received command SLEEP 1500 389s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:29.249: Got a new connection! 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.249: Got instructions of length 14 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.249: Received command SCAN foo-print 389s (process:1980): libfprint-device-DEBUG: 05:08:29.249: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.249: Processing command SLEEP 1500 389s (process:1980): libfprint-virtual_device-DEBUG: 05:08:29.249: Sleeping 1500ms 389s (process:1980): libfprint-device-DEBUG: 05:08:29.549: Idle cancelling on ongoing operation! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.750: Sleeping completed 390s (process:1980): libfprint-device-DEBUG: 05:08:30.750: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.750: Virtual device scan failed with error: Operation was cancelled 390s (process:1980): libfprint-device-DEBUG: 05:08:30.750: Device reported verify completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.750: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1980): libfprint-device-DEBUG: 05:08:30.750: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.750: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.751: Processing command SCAN foo-print 390s (process:1980): libfprint-device-DEBUG: 05:08:30.751: Device reported close completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.751: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.751: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s ok 390s test_enroll (__main__.VirtualDevice.test_enroll) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.751: 130969745365: ../libfprint/drivers/virtual-device.c:387 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.751: 130969745396: ../libfprint/drivers/virtual-device-listener.c:153 390s (process:1980): libfprint-device-DEBUG: 05:08:30.751: Device reported open completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.751: Completing action FPI_DEVICE_ACTION_OPEN in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.751: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.752: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.752: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.752: Received command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.752: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.752: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.752: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.752: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.752: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.752: Device reported enroll progress, reported 1 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.752: Sleeping completed 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.752: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.752: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.752: Received command SCAN testprint 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.752: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.752: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.752: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.752: Device reported enroll progress, reported 2 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.752: Sleeping completed 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.753: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.753: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.753: Received command SCAN testprint 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.753: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Device reported enroll progress, reported 3 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.753: Sleeping completed 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.753: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.753: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.753: Received command SCAN testprint 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.753: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Device reported enroll progress, reported 4 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.753: Sleeping completed 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.753: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.753: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.753: Received command SCAN testprint 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.753: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Device reported enroll progress, reported 5 of 5 have been completed 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Device reported enroll completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Print for finger FP_FINGER_LEFT_LITTLE enrolled 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.753: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.754: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.754: Got instructions of length 16 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.754: Received command SET_KEEP_ALIVE 0 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.754: Keep alive toggled: 0 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.754: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.754: Got instructions of length 19 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.754: Received command SET_ENROLL_STAGES 5 390s (process:1980): libfprint-device-DEBUG: 05:08:30.754: Device reported close completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.754: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.754: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s Enroll done 390s ok 390s test_enroll_script (__main__.VirtualDevice.test_enroll_script) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.754: 130969748378: ../libfprint/drivers/virtual-device.c:387 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.754: 130969748396: ../libfprint/drivers/virtual-device-listener.c:153 390s (process:1980): libfprint-device-DEBUG: 05:08:30.754: Device reported open completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.754: Completing action FPI_DEVICE_ACTION_OPEN in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.754: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.754: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Got instructions of length 19 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Received command SET_ENROLL_STAGES 8 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.755: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Received command SCAN print-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.755: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Received command SCAN print-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.755: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Got instructions of length 7 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Received command RETRY 1 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.755: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Received command SCAN print-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.755: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Got instructions of length 7 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.755: Received command RETRY 3 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.756: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Received command SCAN print-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.756: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Got instructions of length 7 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Received command RETRY 2 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.756: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Received command SCAN print-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.756: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Got instructions of length 8 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Received command SLEEP 10 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.756: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Got instructions of length 8 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Received command SLEEP 20 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.756: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Got instructions of length 7 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.756: Received command RETRY 0 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.757: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.757: Got instructions of length 7 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.757: Received command RETRY 3 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.757: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.757: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.757: Received command SCAN print-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.757: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.757: Got instructions of length 15 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.757: Received command SCAN another-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.757: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.757: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.757: Received command SCAN print-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.757: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.757: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.757: Received command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.757: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.757: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.757: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.757: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.757: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.757: Device reported enroll progress, reported 1 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported enroll progress, reported 2 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Processing command RETRY 1 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported enroll progress, reported 2 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported enroll progress, reported 3 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Processing command RETRY 3 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported enroll progress, reported 3 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported enroll progress, reported 4 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Processing command RETRY 2 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported enroll progress, reported 4 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.758: Device reported enroll progress, reported 5 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Processing command SLEEP 10 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.758: Sleeping 10ms 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.768: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.768: Processing command SLEEP 20 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.768: Sleeping 20ms 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Processing command RETRY 0 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported enroll progress, reported 5 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Processing command RETRY 3 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported enroll progress, reported 5 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported enroll progress, reported 6 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Processing command SCAN another-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported enroll progress, reported 6 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported enroll progress, reported 7 of 8 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.788: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported enroll progress, reported 8 of 8 have been completed 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported enroll completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Print for finger FP_FINGER_UNKNOWN enrolled 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.788: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.789: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.789: Got instructions of length 16 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.789: Received command SET_KEEP_ALIVE 0 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.789: Keep alive toggled: 0 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.789: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.789: Got instructions of length 19 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.789: Received command SET_ENROLL_STAGES 5 390s (process:1980): libfprint-device-DEBUG: 05:08:30.789: Device reported close completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.789: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.789: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s ok 390s test_enroll_script_interactive (__main__.VirtualDevice.test_enroll_script_interactive) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.789: 130969783707: ../libfprint/drivers/virtual-device.c:387 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.790: 130969783725: ../libfprint/drivers/virtual-device-listener.c:153 390s (process:1980): libfprint-device-DEBUG: 05:08:30.790: Device reported open completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.790: Completing action FPI_DEVICE_ACTION_OPEN in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.790: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.790: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.790: Got instructions of length 8 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.790: Received command SLEEP 50 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.790: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.790: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.790: Received command SCAN print-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.790: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.790: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.790: Received command SCAN print-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.791: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.791: Got instructions of length 7 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.791: Received command RETRY 1 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.791: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.791: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.791: Received command SCAN print-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.791: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.791: Got instructions of length 8 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.791: Received command SLEEP 50 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.791: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.791: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.791: Received command SCAN print-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.791: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.791: Got instructions of length 7 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.791: Received command RETRY 2 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.791: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.792: Got instructions of length 15 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.792: Received command SCAN another-id 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.792: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.792: Got instructions of length 13 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.792: Received command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.792: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.792: Processing command SLEEP 50 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.792: Sleeping 50ms 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.842: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.842: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.842: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.842: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.842: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.842: Device reported enroll progress, reported 1 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.842: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.842: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.842: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.842: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.842: Device reported enroll progress, reported 2 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.842: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.842: Processing command RETRY 1 390s (process:1980): libfprint-device-DEBUG: 05:08:30.842: Device reported enroll progress, reported 2 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.842: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.842: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.842: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.842: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.842: Device reported enroll progress, reported 3 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.842: Processing command SLEEP 50 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.842: Sleeping 50ms 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.893: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.893: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Device reported enroll progress, reported 4 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.893: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.893: Processing command RETRY 2 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Device reported enroll progress, reported 4 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.893: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.893: Processing command SCAN another-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Device reported enroll progress, reported 4 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.893: Sleeping completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.893: Processing command SCAN print-id 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Device reported enroll progress, reported 5 of 5 have been completed 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Device reported enroll completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Print for finger FP_FINGER_UNKNOWN enrolled 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.893: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.894: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.894: Got instructions of length 16 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.894: Received command SET_KEEP_ALIVE 0 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.894: Keep alive toggled: 0 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.894: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.894: Got instructions of length 19 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.894: Received command SET_ENROLL_STAGES 5 390s (process:1980): libfprint-device-DEBUG: 05:08:30.894: Device reported close completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.894: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.894: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s ok 390s test_enroll_verify_error (__main__.VirtualDevice.test_enroll_verify_error) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.894: 130969888697: ../libfprint/drivers/virtual-device.c:387 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.895: 130969888724: ../libfprint/drivers/virtual-device-listener.c:153 390s (process:1980): libfprint-device-DEBUG: 05:08:30.895: Device reported open completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.895: Completing action FPI_DEVICE_ACTION_OPEN in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.895: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.895: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.895: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.895: Received command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.895: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.895: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.895: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.895: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.895: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.895: Device reported enroll progress, reported 1 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.895: Sleeping completed 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.896: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.896: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.896: Received command SCAN testprint 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.896: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.896: Device reported enroll progress, reported 2 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.896: Sleeping completed 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.896: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.896: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.896: Received command SCAN testprint 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.896: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.896: Device reported enroll progress, reported 3 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.896: Sleeping completed 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.896: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.896: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.896: Received command SCAN testprint 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.896: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.896: Device reported enroll progress, reported 4 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.897: Sleeping completed 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.897: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.897: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.897: Received command SCAN testprint 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.897: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.897: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.897: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.897: Device reported enroll progress, reported 5 of 5 have been completed 390s (process:1980): libfprint-device-DEBUG: 05:08:30.897: Device reported enroll completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.897: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1980): libfprint-device-DEBUG: 05:08:30.897: Print for finger FP_FINGER_LEFT_RING enrolled 390s (process:1980): libfprint-device-DEBUG: 05:08:30.897: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.897: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.897: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.897: Got instructions of length 7 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.897: Received command ERROR 0 390s (process:1980): libfprint-device-DEBUG: 05:08:30.897: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.897: Processing command ERROR 0 390s (process:1980): libfprint-device-DEBUG: 05:08:30.898: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.898: Virtual device scan failed with error: An unspecified error occurred! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.898: Device reported verify completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.898: Device reported finger status change: FP_FINGER_STATUS_NONE 390s (process:1980): libfprint-device-DEBUG: 05:08:30.898: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.898: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.898: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.898: Got instructions of length 16 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.898: Received command SET_KEEP_ALIVE 0 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.898: Keep alive toggled: 0 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.898: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.898: Got instructions of length 19 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.898: Received command SET_ENROLL_STAGES 5 390s (process:1980): libfprint-device-DEBUG: 05:08:30.898: Device reported close completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.898: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.898: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s Enroll done 390s ok 390s test_enroll_verify_match (__main__.VirtualDevice.test_enroll_verify_match) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.898: 130969892532: ../libfprint/drivers/virtual-device.c:387 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.898: 130969892547: ../libfprint/drivers/virtual-device-listener.c:153 390s (process:1980): libfprint-device-DEBUG: 05:08:30.898: Device reported open completion 390s (process:1980): libfprint-device-DEBUG: 05:08:30.899: Completing action FPI_DEVICE_ACTION_OPEN in idle! 390s (process:1980): libfprint-device-DEBUG: 05:08:30.899: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.899: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.899: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.899: Received command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.899: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.899: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.899: Device reported enroll progress, reported 1 of 5 have been completed 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.899: Sleeping completed 390s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.899: Got a new connection! 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.899: Got instructions of length 14 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.899: Received command SCAN testprint 390s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.899: Processing command SCAN testprint 390s (process:1980): libfprint-device-DEBUG: 05:08:30.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 390s (process:1980): libfprint-device-DEBUG: 05:08:30.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED 390s (process:1980): libfprint-device-DEBUG: 05:08:30.899: Device reported enroll progress, reported 2 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.899: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.899: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.899: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.900: Received command SCAN testprint 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.900: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Device reported enroll progress, reported 3 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.900: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.900: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.900: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.900: Received command SCAN testprint 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.900: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Device reported enroll progress, reported 4 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.900: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.900: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.900: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.900: Received command SCAN testprint 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.900: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Device reported enroll progress, reported 5 of 5 have been completed 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Device reported enroll completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Print for finger FP_FINGER_LEFT_THUMB enrolled 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.900: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.900: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.901: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.901: Received command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.901: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.901: Virtual device scanned print testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Device reported verify result 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Device reported verify completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.901: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.901: Got instructions of length 16 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.901: Received command SET_KEEP_ALIVE 0 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.901: Keep alive toggled: 0 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.901: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.901: Got instructions of length 19 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.901: Received command SET_ENROLL_STAGES 5 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.901: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s Enroll done 391s ok 391s test_enroll_verify_no_match (__main__.VirtualDevice.test_enroll_verify_no_match) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.902: 130969895819: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.902: 130969895836: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:30.902: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.902: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.902: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.902: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.902: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.902: Received command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.902: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.902: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.902: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.902: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.902: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.902: Device reported enroll progress, reported 1 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.902: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.902: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Received command SCAN testprint 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.903: Device reported enroll progress, reported 2 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.903: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Received command SCAN testprint 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.903: Device reported enroll progress, reported 3 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.903: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Received command SCAN testprint 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.903: Device reported enroll progress, reported 4 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.903: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.903: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.904: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.904: Received command SCAN testprint 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.904: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Device reported enroll progress, reported 5 of 5 have been completed 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Device reported enroll completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Print for finger FP_FINGER_LEFT_RING enrolled 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.904: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.904: Got instructions of length 18 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.904: Received command SCAN not-testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.904: Processing command SCAN not-testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.904: Virtual device scanned print not-testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Device reported verify result 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Device reported verify completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.904: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.904: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.904: Got instructions of length 16 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.904: Received command SET_KEEP_ALIVE 0 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.904: Keep alive toggled: 0 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.905: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.905: Got instructions of length 19 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.905: Received command SET_ENROLL_STAGES 5 391s (process:1980): libfprint-device-DEBUG: 05:08:30.905: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.905: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.905: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s Enroll done 391s ok 391s test_enroll_verify_retry (__main__.VirtualDevice.test_enroll_verify_retry) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.905: 130969899153: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.905: 130969899170: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:30.905: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.905: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.905: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.905: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.905: Got instructions of length 7 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.905: Received command RETRY 1 391s (process:1980): libfprint-device-DEBUG: 05:08:30.906: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.906: Processing command RETRY 1 391s (process:1980): libfprint-device-DEBUG: 05:08:30.906: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.906: Virtual device scan failed with error: The swipe was too short, please try again. 391s (process:1980): libfprint-device-DEBUG: 05:08:30.906: Device reported verify result 391s (process:1980): libfprint-device-DEBUG: 05:08:30.906: Device reported verify completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.906: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:30.906: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.906: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.906: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.906: Got instructions of length 16 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.906: Received command SET_KEEP_ALIVE 0 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.906: Keep alive toggled: 0 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.906: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.906: Got instructions of length 19 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.906: Received command SET_ENROLL_STAGES 5 391s (process:1980): libfprint-device-DEBUG: 05:08:30.906: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.906: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.906: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s ok 391s test_enroll_verify_script (__main__.VirtualDevice.test_enroll_verify_script) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.906: 130969900596: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.906: 130969900612: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:30.907: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.907: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.907: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.907: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.907: Got instructions of length 19 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.907: Received command SET_ENROLL_STAGES 8 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.907: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.907: Got instructions of length 13 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.907: Received command SCAN print-id 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.907: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.907: Got instructions of length 13 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.907: Received command SCAN print-id 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.907: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.907: Got instructions of length 7 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.907: Received command RETRY 1 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.907: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Got instructions of length 13 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Received command SCAN print-id 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.908: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Got instructions of length 7 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Received command RETRY 3 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.908: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Got instructions of length 13 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Received command SCAN print-id 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.908: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Got instructions of length 7 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Received command RETRY 2 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.908: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Got instructions of length 13 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Received command SCAN print-id 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.908: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Got instructions of length 8 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.908: Received command SLEEP 10 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.909: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Got instructions of length 8 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Received command SLEEP 20 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.909: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Got instructions of length 7 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Received command RETRY 0 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.909: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Got instructions of length 7 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Received command RETRY 3 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.909: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Got instructions of length 13 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Received command SCAN print-id 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.909: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Got instructions of length 15 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Received command SCAN another-id 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.909: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Got instructions of length 13 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.909: Received command SCAN print-id 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.910: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Got instructions of length 13 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Received command SCAN print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Processing command SCAN print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported enroll progress, reported 1 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Processing command SCAN print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported enroll progress, reported 2 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Processing command RETRY 1 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported enroll progress, reported 2 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Processing command SCAN print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported enroll progress, reported 3 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Processing command RETRY 3 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported enroll progress, reported 3 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Processing command SCAN print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported enroll progress, reported 4 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Processing command RETRY 2 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported enroll progress, reported 4 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Processing command SCAN print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.910: Device reported enroll progress, reported 5 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Processing command SLEEP 10 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.910: Sleeping 10ms 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.920: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.920: Processing command SLEEP 20 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.920: Sleeping 20ms 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.940: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.940: Processing command RETRY 0 391s (process:1980): libfprint-device-DEBUG: 05:08:30.940: Device reported enroll progress, reported 5 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.940: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.940: Processing command RETRY 3 391s (process:1980): libfprint-device-DEBUG: 05:08:30.940: Device reported enroll progress, reported 5 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.940: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.940: Processing command SCAN print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.940: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.940: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.940: Device reported enroll progress, reported 6 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.941: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.941: Processing command SCAN another-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported enroll progress, reported 6 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.941: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.941: Processing command SCAN print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported enroll progress, reported 7 of 8 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.941: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.941: Processing command SCAN print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported enroll progress, reported 8 of 8 have been completed 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported enroll completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Print for finger FP_FINGER_UNKNOWN enrolled 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.941: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.941: Got instructions of length 7 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.941: Received command RETRY 2 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.941: Processing command RETRY 2 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.941: Virtual device scan failed with error: The finger was not centered properly, please try again. 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported verify result 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported verify completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.941: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.942: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.942: Got instructions of length 8 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.942: Received command SLEEP 50 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.942: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.942: Got instructions of length 7 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.942: Received command RETRY 1 391s (process:1980): libfprint-device-DEBUG: 05:08:30.942: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.942: Processing command SLEEP 50 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.942: Sleeping 50ms 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.992: Sleeping completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.992: Processing command RETRY 1 391s (process:1980): libfprint-device-DEBUG: 05:08:30.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.992: Virtual device scan failed with error: The swipe was too short, please try again. 391s (process:1980): libfprint-device-DEBUG: 05:08:30.992: Device reported verify result 391s (process:1980): libfprint-device-DEBUG: 05:08:30.992: Device reported verify completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.992: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:30.992: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.992: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.993: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.993: Got instructions of length 15 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.993: Received command SCAN another-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.993: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.993: Processing command SCAN another-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.993: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.993: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.993: Virtual device scanned print another-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.993: Device reported verify result 391s (process:1980): libfprint-device-DEBUG: 05:08:30.993: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.993: Device reported verify completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.993: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:30.993: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.993: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.994: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.994: Got instructions of length 13 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.994: Received command SCAN print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.994: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.994: Processing command SCAN print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.994: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.994: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.994: Virtual device scanned print print-id 391s (process:1980): libfprint-device-DEBUG: 05:08:30.994: Device reported verify result 391s (process:1980): libfprint-device-DEBUG: 05:08:30.994: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.994: Device reported verify completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.994: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:30.994: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.994: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.994: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.994: Got instructions of length 16 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.994: Received command SET_KEEP_ALIVE 0 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.994: Keep alive toggled: 0 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.995: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.995: Got instructions of length 19 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.995: Received command SET_ENROLL_STAGES 5 391s (process:1980): libfprint-device-DEBUG: 05:08:30.995: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.995: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.995: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s ok 391s test_enroll_with_retry (__main__.VirtualDevice.test_enroll_with_retry) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.995: 130969989200: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.995: 130969989230: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:30.995: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.995: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.995: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.996: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.996: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.996: Received command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.996: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.996: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.996: Device reported enroll progress, reported 1 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.996: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.996: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.996: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.996: Received command SCAN testprint 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.996: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.996: Device reported enroll progress, reported 2 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.996: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.997: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.997: Got instructions of length 7 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.997: Received command RETRY 1 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.997: Processing command RETRY 1 391s (process:1980): libfprint-device-DEBUG: 05:08:30.997: Device reported enroll progress, reported 2 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.997: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.997: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.997: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.997: Received command SCAN testprint 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.997: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.997: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.997: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.997: Device reported enroll progress, reported 3 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.997: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.997: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.997: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.997: Received command SCAN testprint 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.997: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.997: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.998: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.998: Device reported enroll progress, reported 4 of 5 have been completed 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.998: Sleeping completed 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.998: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.998: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.998: Received command SCAN testprint 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.998: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:30.998: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:30.998: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:30.998: Device reported enroll progress, reported 5 of 5 have been completed 391s (process:1980): libfprint-device-DEBUG: 05:08:30.998: Device reported enroll completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.998: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:30.998: Print for finger FP_FINGER_LEFT_LITTLE enrolled 391s (process:1980): libfprint-device-DEBUG: 05:08:30.998: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.998: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.998: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.998: Got instructions of length 16 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.998: Received command SET_KEEP_ALIVE 0 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.998: Keep alive toggled: 0 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.998: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.998: Got instructions of length 19 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.998: Received command SET_ENROLL_STAGES 5 391s (process:1980): libfprint-device-DEBUG: 05:08:30.999: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.999: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.999: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s Enroll done 391s ok 391s test_finger_status (__main__.VirtualDevice.test_finger_status) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.999: 130969992929: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.999: 130969992943: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:30.999: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:30.999: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:30.999: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-device-DEBUG: 05:08:30.999: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-device-DEBUG: 05:08:30.999: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.999: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.999: Got instructions of length 8 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.999: Received command FINGER 1 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:30.999: Processing command FINGER 1 391s (process:1980): libfprint-device-DEBUG: 05:08:30.999: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:30.999: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.000: Got instructions of length 8 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.000: Received command FINGER 0 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.000: Processing command FINGER 0 391s (process:1980): libfprint-device-DEBUG: 05:08:31.000: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:31.000: Idle cancelling on ongoing operation! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.000: Got cancellation! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.000: Virtual device scan failed with error: Operation was cancelled 391s (process:1980): libfprint-device-DEBUG: 05:08:31.000: Device reported verify completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.000: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:31.000: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.000: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.000: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.000: Got instructions of length 16 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.000: Received command SET_KEEP_ALIVE 0 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.000: Keep alive toggled: 0 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.000: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.000: Got instructions of length 19 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.000: Received command SET_ENROLL_STAGES 5 391s (process:1980): libfprint-device-DEBUG: 05:08:31.000: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.000: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.000: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s ok 391s test_finger_status_after_sleep (__main__.VirtualDevice.test_finger_status_after_sleep) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.000: 130969994600: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.000: 130969994614: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:31.001: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.001: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.001: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.001: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.001: Got instructions of length 8 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.001: Received command SLEEP 10 391s (process:1980): libfprint-device-DEBUG: 05:08:31.001: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.001: Processing command SLEEP 10 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.001: Sleeping 10ms 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.011: Sleeping completed 391s (process:1980): libfprint-device-DEBUG: 05:08:31.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.012: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.012: Got instructions of length 8 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.012: Received command FINGER 1 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.012: Processing command FINGER 1 391s (process:1980): libfprint-device-DEBUG: 05:08:31.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.012: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.012: Got instructions of length 8 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.012: Received command FINGER 0 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.012: Processing command FINGER 0 391s (process:1980): libfprint-device-DEBUG: 05:08:31.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:31.012: Idle cancelling on ongoing operation! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.012: Got cancellation! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.012: Virtual device scan failed with error: Operation was cancelled 391s (process:1980): libfprint-device-DEBUG: 05:08:31.012: Device reported verify completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.012: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:31.012: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.012: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.013: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.013: Got instructions of length 16 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.013: Received command SET_KEEP_ALIVE 0 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.013: Keep alive toggled: 0 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.013: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.013: Got instructions of length 19 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.013: Received command SET_ENROLL_STAGES 5 391s (process:1980): libfprint-device-DEBUG: 05:08:31.013: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.013: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.013: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s ok 391s test_identify_unsupported (__main__.VirtualDevice.test_identify_unsupported) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.013: 130970007548: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.013: 130970007565: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:31.014: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.014: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.014: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.014: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.014: Got instructions of length 16 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.014: Received command SET_KEEP_ALIVE 0 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.014: Keep alive toggled: 0 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.014: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.014: Got instructions of length 19 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.014: Received command SET_ENROLL_STAGES 5 391s (process:1980): libfprint-device-DEBUG: 05:08:31.014: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.014: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.014: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s ok 391s test_open_error (__main__.VirtualDevice.test_open_error) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.015: 130970008790: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.015: 130970008804: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:31.015: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.015: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.015: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.015: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.015: Got instructions of length 16 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.015: Received command IGNORED_COMMAND 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.015: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.015: Got instructions of length 7 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.015: Received command ERROR 5 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.015: Processing command IGNORED_COMMAND 391s (process:1980): libfprint-device-DEBUG: 05:08:31.015: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.015: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.015: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.016: 130970009777: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.016: Processing command ERROR 5 391s (process:1980): libfprint-device-DEBUG: 05:08:31.016: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.016: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.016: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s ok 391s test_open_error_with_keep_alive (__main__.VirtualDevice.test_open_error_with_keep_alive) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.016: 130970009968: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.016: 130970009984: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:31.016: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.016: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.016: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.016: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.016: Got instructions of length 16 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.016: Received command SET_KEEP_ALIVE 1 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.016: Keep alive toggled: 1 391s (process:1980): libfprint-device-DEBUG: 05:08:31.016: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.016: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.016: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.016: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.016: Got instructions of length 7 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.016: Received command ERROR 5 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.016: 130970010715: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.017: Processing command ERROR 5 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s ok 391s test_quick_enroll (__main__.VirtualDevice.test_quick_enroll) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.017: 130970010887: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.017: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.017: Got instructions of length 19 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.017: Received command SET_ENROLL_STAGES 1 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.017: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.017: Got instructions of length 14 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.017: Received command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.017: Processing command SCAN testprint 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Device reported enroll progress, reported 1 of 1 have been completed 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Device reported enroll completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Device reported finger status change: FP_FINGER_STATUS_NONE 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Print for finger FP_FINGER_LEFT_LITTLE enrolled 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.018: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.018: Got instructions of length 16 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.018: Received command SET_KEEP_ALIVE 0 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.018: Keep alive toggled: 0 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.018: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.018: Got instructions of length 19 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.018: Received command SET_ENROLL_STAGES 5 391s (process:1980): libfprint-device-DEBUG: 05:08:31.018: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.018: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.018: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 391s Enroll done 391s ok 391s (process:1980): libfprint-context-DEBUG: 05:08:31.019: Initializing FpContext (libfprint version 1.94.9+tod1) 391s (process:1980): libfprint-tod-DEBUG: 05:08:31.019: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 391s (process:1980): libfprint-context-DEBUG: 05:08:31.021: No driver found for USB device 1D6B:0003 391s (process:1980): libfprint-context-DEBUG: 05:08:31.021: No driver found for USB device 0627:0001 391s (process:1980): libfprint-context-DEBUG: 05:08:31.021: No driver found for USB device 1D6B:0002 391s (process:1980): libfprint-context-DEBUG: 05:08:31.021: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-lnrwgbba/virtual-device.socket 391s (process:1980): libfprint-context-DEBUG: 05:08:31.022: created 391s (process:1980): libfprint-device-DEBUG: 05:08:31.022: Device reported probe completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.022: Completing action FPI_DEVICE_ACTION_PROBE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.022: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 391s test_capture (__main__.VirtualDeviceBusyDeviceOperations.test_capture) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.023: 130970016858: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.023: 130970016880: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:31.023: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.023: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.023: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.023: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.023: Got instructions of length 9 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.023: Received command SLEEP 200 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.023: Processing command SLEEP 200 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.023: Sleeping 200ms 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.223: Sleeping completed 391s (process:1980): libfprint-device-DEBUG: 05:08:31.223: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.224: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.224: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 391s ok 391s test_close (__main__.VirtualDeviceBusyDeviceOperations.test_close) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.224: 130970217983: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.224: 130970217996: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:31.224: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.224: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.224: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.224: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.224: Got instructions of length 9 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.224: Received command SLEEP 200 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.224: Processing command SLEEP 200 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.224: Sleeping 200ms 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.425: Sleeping completed 391s (process:1980): libfprint-device-DEBUG: 05:08:31.425: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.425: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.425: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 391s ok 391s test_delete_print (__main__.VirtualDeviceBusyDeviceOperations.test_delete_print) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.425: 130970419485: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.425: 130970419508: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:31.425: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.426: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.426: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.426: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.426: Got instructions of length 9 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.426: Received command SLEEP 200 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.426: Processing command SLEEP 200 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.426: Sleeping 200ms 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.626: Sleeping completed 391s (process:1980): libfprint-device-DEBUG: 05:08:31.626: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.627: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.627: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 391s ok 391s test_enroll (__main__.VirtualDeviceBusyDeviceOperations.test_enroll) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.627: 130970620959: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.627: 130970620978: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:31.628: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.628: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.628: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.628: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.628: Got instructions of length 9 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.628: Received command SLEEP 200 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.628: Processing command SLEEP 200 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.628: Sleeping 200ms 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.828: Sleeping completed 391s (process:1980): libfprint-device-DEBUG: 05:08:31.829: Device reported close completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.829: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.829: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 391s ok 391s test_identify (__main__.VirtualDeviceBusyDeviceOperations.test_identify) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.829: 130970823139: ../libfprint/drivers/virtual-device.c:387 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.829: 130970823160: ../libfprint/drivers/virtual-device-listener.c:153 391s (process:1980): libfprint-device-DEBUG: 05:08:31.829: Device reported open completion 391s (process:1980): libfprint-device-DEBUG: 05:08:31.829: Completing action FPI_DEVICE_ACTION_OPEN in idle! 391s (process:1980): libfprint-device-DEBUG: 05:08:31.829: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 391s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:31.829: Got a new connection! 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.830: Got instructions of length 9 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.830: Received command SLEEP 200 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.830: Processing command SLEEP 200 391s (process:1980): libfprint-virtual_device-DEBUG: 05:08:31.830: Sleeping 200ms 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.030: Sleeping completed 392s (process:1980): libfprint-device-DEBUG: 05:08:32.030: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.030: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.030: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_list_prints (__main__.VirtualDeviceBusyDeviceOperations.test_list_prints) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.030: 130971024626: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.030: 130971024647: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.031: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.031: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.031: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.031: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.031: Got instructions of length 9 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.031: Received command SLEEP 200 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.031: Processing command SLEEP 200 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.031: Sleeping 200ms 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.232: Sleeping completed 392s (process:1980): libfprint-device-DEBUG: 05:08:32.232: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.232: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.232: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_open (__main__.VirtualDeviceBusyDeviceOperations.test_open) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.232: 130971226361: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.232: 130971226384: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.232: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.232: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.232: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.233: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.233: Got instructions of length 9 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.233: Received command SLEEP 200 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.233: Processing command SLEEP 200 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.233: Sleeping 200ms 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.233: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.233: Got instructions of length 16 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.233: Received command SET_KEEP_ALIVE 1 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.233: Keep alive toggled: 1 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.433: Sleeping completed 392s (process:1980): libfprint-device-DEBUG: 05:08:32.433: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.433: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.433: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.434: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.434: Got instructions of length 9 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.434: Received command SLEEP 100 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.434: 130971427965: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.434: Processing command SLEEP 100 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.434: Sleeping 100ms 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.534: Sleeping completed 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.534: 130971528127: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-device-DEBUG: 05:08:32.534: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.534: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.534: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-device-DEBUG: 05:08:32.534: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.534: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.534: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_verify (__main__.VirtualDeviceBusyDeviceOperations.test_verify) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.534: 130971528554: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-device-DEBUG: 05:08:32.534: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.534: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.534: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.535: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.535: Got instructions of length 9 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.535: Received command SLEEP 200 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.535: Processing command SLEEP 200 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.535: Sleeping 200ms 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.735: Sleeping completed 392s (process:1980): libfprint-device-DEBUG: 05:08:32.735: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.735: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.735: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.736: 130971730070: ../libfprint/drivers/virtual-device.c:752 392s (process:1980): libfprint-context-DEBUG: 05:08:32.736: Initializing FpContext (libfprint version 1.94.9+tod1) 392s (process:1980): libfprint-tod-DEBUG: 05:08:32.737: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 392s (process:1980): libfprint-context-DEBUG: 05:08:32.739: No driver found for USB device 1D6B:0003 392s (process:1980): libfprint-context-DEBUG: 05:08:32.739: No driver found for USB device 0627:0001 392s (process:1980): libfprint-context-DEBUG: 05:08:32.739: No driver found for USB device 1D6B:0002 392s (process:1980): libfprint-context-DEBUG: 05:08:32.739: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-qqg8c__8/virtual-device.socket 392s (process:1980): libfprint-context-DEBUG: 05:08:32.739: created 392s (process:1980): libfprint-device-DEBUG: 05:08:32.740: Device reported probe completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.740: Completing action FPI_DEVICE_ACTION_PROBE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.740: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s test_capture (__main__.VirtualDeviceClosed.test_capture) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.740: 130971734231: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.740: 130971734283: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.740: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.740: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.740: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-device-DEBUG: 05:08:32.740: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.740: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.740: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_close (__main__.VirtualDeviceClosed.test_close) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.741: 130971734868: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.741: 130971734895: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.741: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.741: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.741: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-device-DEBUG: 05:08:32.741: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.741: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.741: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_delete_print (__main__.VirtualDeviceClosed.test_delete_print) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.741: 130971735535: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.741: 130971735553: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.741: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.741: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.742: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-device-DEBUG: 05:08:32.742: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.742: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.742: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_enroll (__main__.VirtualDeviceClosed.test_enroll) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.742: 130971736116: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.742: 130971736174: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.742: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.742: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.742: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-device-DEBUG: 05:08:32.742: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.742: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.742: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_identify (__main__.VirtualDeviceClosed.test_identify) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.743: 130971736810: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.743: 130971736827: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.743: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.743: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.743: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-device-DEBUG: 05:08:32.743: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.743: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.743: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_list_prints (__main__.VirtualDeviceClosed.test_list_prints) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.743: 130971737471: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.743: 130971737489: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.743: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.743: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.743: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-device-DEBUG: 05:08:32.744: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.744: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.744: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_verify (__main__.VirtualDeviceClosed.test_verify) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.744: 130971737988: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.744: 130971738066: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.744: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.744: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.744: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-device-DEBUG: 05:08:32.744: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.744: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.744: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.745: 130971738808: ../libfprint/drivers/virtual-device.c:752 392s (process:1980): libfprint-context-DEBUG: 05:08:32.745: Initializing FpContext (libfprint version 1.94.9+tod1) 392s (process:1980): libfprint-tod-DEBUG: 05:08:32.745: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 392s (process:1980): libfprint-context-DEBUG: 05:08:32.747: No driver found for USB device 1D6B:0003 392s (process:1980): libfprint-context-DEBUG: 05:08:32.747: No driver found for USB device 0627:0001 392s (process:1980): libfprint-context-DEBUG: 05:08:32.747: No driver found for USB device 1D6B:0002 392s (process:1980): libfprint-context-DEBUG: 05:08:32.747: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-qqg8c__8/virtual-device.socket 392s (process:1980): libfprint-context-DEBUG: 05:08:32.748: created 392s (process:1980): libfprint-context-DEBUG: 05:08:32.748: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-6yt098ul/virtual-device-storage.socket 392s (process:1980): libfprint-context-DEBUG: 05:08:32.748: created 392s (process:1980): libfprint-device-DEBUG: 05:08:32.748: Device reported probe completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.748: Device reported probe completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.749: Completing action FPI_DEVICE_ACTION_PROBE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.749: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-device-DEBUG: 05:08:32.749: Completing action FPI_DEVICE_ACTION_PROBE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.749: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s test_capture_unsupported (__main__.VirtualDeviceStorage.test_capture_unsupported) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.749: 130971743173: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.749: 130971743253: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.749: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.749: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.749: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.750: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.750: Got instructions of length 5 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.750: Received command CONT 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.750: Processing command CONT 392s (process:1980): libfprint-device-DEBUG: 05:08:32.750: Device reported deletion completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.750: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.750: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.750: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.750: Got instructions of length 16 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.750: Received command SET_KEEP_ALIVE 0 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.750: Keep alive toggled: 0 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.750: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.751: Got instructions of length 19 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.751: Received command SET_ENROLL_STAGES 5 392s (process:1980): libfprint-device-DEBUG: 05:08:32.751: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.751: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.751: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_change_enroll_stages (__main__.VirtualDeviceStorage.test_change_enroll_stages) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.751: 130971745104: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.751: 130971745130: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.751: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.751: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.751: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.751: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.752: Got instructions of length 20 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.752: Received command SET_ENROLL_STAGES 20 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.752: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.752: Got instructions of length 19 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.752: Received command SET_ENROLL_STAGES 1 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.752: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.752: Got instructions of length 19 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.752: Received command SET_ENROLL_STAGES 0 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.753: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.753: Got instructions of length 5 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.753: Received command CONT 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.753: Processing command CONT 392s (process:1980): libfprint-device-DEBUG: 05:08:32.753: Device reported deletion completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.753: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.753: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.753: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.753: Got instructions of length 16 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.753: Received command SET_KEEP_ALIVE 0 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.753: Keep alive toggled: 0 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.753: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.753: Got instructions of length 19 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.753: Received command SET_ENROLL_STAGES 5 392s (process:1980): libfprint-device-DEBUG: 05:08:32.754: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.754: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.754: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_change_scan_type (__main__.VirtualDeviceStorage.test_change_scan_type) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.754: 130971747979: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.754: 130971747990: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.754: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.754: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.754: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.754: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.754: Got instructions of length 19 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.754: Received command SET_SCAN_TYPE press 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.755: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.755: Got instructions of length 19 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.755: Received command SET_SCAN_TYPE swipe 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.755: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.755: Got instructions of length 25 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.755: Received command SET_SCAN_TYPE eye-contact 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.755: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.755: Got instructions of length 5 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.755: Received command CONT 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.756: Processing command CONT 392s (process:1980): libfprint-device-DEBUG: 05:08:32.756: Device reported deletion completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.756: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.756: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.756: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.756: Got instructions of length 16 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.756: Received command SET_KEEP_ALIVE 0 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.756: Keep alive toggled: 0 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.756: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.756: Got instructions of length 19 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.756: Received command SET_ENROLL_STAGES 5 392s (process:1980): libfprint-device-DEBUG: 05:08:32.756: Device reported close completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.756: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.756: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s ok 392s test_clear_storage (__main__.VirtualDeviceStorage.test_clear_storage) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.757: 130971750776: ../libfprint/drivers/virtual-device.c:387 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.757: 130971750796: ../libfprint/drivers/virtual-device-listener.c:153 392s (process:1980): libfprint-device-DEBUG: 05:08:32.757: Device reported open completion 392s (process:1980): libfprint-device-DEBUG: 05:08:32.757: Completing action FPI_DEVICE_ACTION_OPEN in idle! 392s (process:1980): libfprint-device-DEBUG: 05:08:32.757: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 392s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:32.757: Got a new connection! 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.757: Got instructions of length 9 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.757: Received command INSERT p1 392s (process:1980): libfprint-virtual_device-DEBUG: 05:08:32.757: Processing command INSERT p1 392s Executing: libfprint-2/virtual-device.test 393s (process:1980): libfprint-device-DEBUG: 05:08:33.258: Device reported listing completion 393s (process:1980): libfprint-device-DEBUG: 05:08:33.258: Completing action FPI_DEVICE_ACTION_LIST in idle! 393s (process:1980): libfprint-device-DEBUG: 05:08:33.258: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:33.259: Got a new connection! 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.260: Got instructions of length 5 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.260: Received command CONT 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.260: Processing command CONT 393s (process:1980): libfprint-device-DEBUG: 05:08:33.260: Device reported deletion completion 393s (process:1980): libfprint-device-DEBUG: 05:08:33.260: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 393s (process:1980): libfprint-device-DEBUG: 05:08:33.260: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s (process:1980): libfprint-device-DEBUG: 05:08:33.761: Device reported listing completion 393s (process:1980): libfprint-device-DEBUG: 05:08:33.761: Completing action FPI_DEVICE_ACTION_LIST in idle! 393s (process:1980): libfprint-device-DEBUG: 05:08:33.761: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:33.761: Got a new connection! 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.761: Got instructions of length 5 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.762: Received command CONT 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.762: Processing command CONT 393s (process:1980): libfprint-device-DEBUG: 05:08:33.762: Device reported deletion completion 393s (process:1980): libfprint-device-DEBUG: 05:08:33.762: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 393s (process:1980): libfprint-device-DEBUG: 05:08:33.762: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:33.762: Got a new connection! 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.762: Got instructions of length 16 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.762: Received command SET_KEEP_ALIVE 0 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.762: Keep alive toggled: 0 393s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:33.762: Got a new connection! 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.762: Got instructions of length 19 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.762: Received command SET_ENROLL_STAGES 5 393s (process:1980): libfprint-device-DEBUG: 05:08:33.762: Device reported close completion 393s (process:1980): libfprint-device-DEBUG: 05:08:33.762: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 393s (process:1980): libfprint-device-DEBUG: 05:08:33.762: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s 393s ok 393s test_clear_storage_error (__main__.VirtualDeviceStorage.test_clear_storage_error) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.763: 130972756791: ../libfprint/drivers/virtual-device.c:387 393s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:33.763: 130972756801: ../libfprint/drivers/virtual-device-listener.c:153 393s (process:1980): libfprint-device-DEBUG: 05:08:33.763: Device reported open completion 393s (process:1980): libfprint-device-DEBUG: 05:08:33.763: Completing action FPI_DEVICE_ACTION_OPEN in idle! 393s (process:1980): libfprint-device-DEBUG: 05:08:33.763: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 393s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:33.763: Got a new connection! 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.763: Got instructions of length 9 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.763: Received command INSERT p1 393s (process:1980): libfprint-virtual_device-DEBUG: 05:08:33.763: Processing command INSERT p1 394s (process:1980): libfprint-device-DEBUG: 05:08:34.264: Device reported listing completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.264: Completing action FPI_DEVICE_ACTION_LIST in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.264: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.265: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.266: Got instructions of length 7 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.266: Received command ERROR 5 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.266: Processing command ERROR 5 394s (process:1980): libfprint-device-DEBUG: 05:08:34.266: Device reported deletion completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.266: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.266: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.267: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.267: Got instructions of length 5 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.267: Received command CONT 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.267: Processing command CONT 394s (process:1980): libfprint-device-DEBUG: 05:08:34.267: Device reported deletion completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.267: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.267: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.267: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.268: Got instructions of length 16 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.268: Received command SET_KEEP_ALIVE 0 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.268: Keep alive toggled: 0 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.268: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.268: Got instructions of length 19 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.268: Received command SET_ENROLL_STAGES 5 394s (process:1980): libfprint-device-DEBUG: 05:08:34.269: Device reported close completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.269: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.269: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s 394s ok 394s test_close_error (__main__.VirtualDeviceStorage.test_close_error) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.269: 130973263634: ../libfprint/drivers/virtual-device.c:387 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.269: 130973263702: ../libfprint/drivers/virtual-device-listener.c:153 394s (process:1980): libfprint-device-DEBUG: 05:08:34.270: Device reported open completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.270: Completing action FPI_DEVICE_ACTION_OPEN in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.270: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.271: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.271: Got instructions of length 9 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.271: Received command SLEEP 100 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.272: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.272: Got instructions of length 7 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.272: Received command ERROR 4 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.272: Processing command SLEEP 100 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.272: Sleeping 100ms 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.372: Sleeping completed 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.372: Processing command ERROR 4 394s (process:1980): libfprint-device-DEBUG: 05:08:34.372: Device reported close completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.373: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.373: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s ok 394s test_close_while_opening (__main__.VirtualDeviceStorage.test_close_while_opening) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.373: 130973367687: ../libfprint/drivers/virtual-device.c:387 394s (process:1980): libfprint-device-DEBUG: 05:08:34.374: Device reported open completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.374: Completing action FPI_DEVICE_ACTION_OPEN in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.374: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.374: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.375: Got instructions of length 16 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.375: Received command SET_KEEP_ALIVE 1 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.375: Keep alive toggled: 1 394s (process:1980): libfprint-device-DEBUG: 05:08:34.375: Device reported close completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.375: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.375: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.376: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.376: Got instructions of length 9 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.376: Received command SLEEP 500 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.376: 130973370450: ../libfprint/drivers/virtual-device.c:387 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.376: Processing command SLEEP 500 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.376: Sleeping 500ms 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.877: Sleeping completed 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.877: 130973871195: ../libfprint/drivers/virtual-device.c:387 394s (process:1980): libfprint-device-DEBUG: 05:08:34.877: Device reported open completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.877: Completing action FPI_DEVICE_ACTION_OPEN in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.877: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.877: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.878: Got instructions of length 5 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.878: Received command CONT 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.878: Processing command CONT 394s (process:1980): libfprint-device-DEBUG: 05:08:34.878: Device reported deletion completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.878: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.878: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.878: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.878: Got instructions of length 16 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.878: Received command SET_KEEP_ALIVE 0 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.878: Keep alive toggled: 0 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.878: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.878: Got instructions of length 19 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.878: Received command SET_ENROLL_STAGES 5 394s (process:1980): libfprint-device-DEBUG: 05:08:34.878: Device reported close completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.878: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.878: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s ok 394s test_delayed_open (__main__.VirtualDeviceStorage.test_delayed_open) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.879: 130973872796: ../libfprint/drivers/virtual-device.c:387 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.879: 130973872815: ../libfprint/drivers/virtual-device-listener.c:153 394s (process:1980): libfprint-device-DEBUG: 05:08:34.879: Device reported open completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.879: Completing action FPI_DEVICE_ACTION_OPEN in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.879: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.879: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.879: Got instructions of length 16 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.879: Received command IGNORED_COMMAND 394s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:34.879: Got a new connection! 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.879: Got instructions of length 9 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.879: Received command SLEEP 500 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.879: Processing command IGNORED_COMMAND 394s (process:1980): libfprint-device-DEBUG: 05:08:34.880: Device reported close completion 394s (process:1980): libfprint-device-DEBUG: 05:08:34.880: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 394s (process:1980): libfprint-device-DEBUG: 05:08:34.880: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.880: 130973874109: ../libfprint/drivers/virtual-device.c:387 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.880: Processing command SLEEP 500 394s (process:1980): libfprint-virtual_device-DEBUG: 05:08:34.880: Sleeping 500ms 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.381: Sleeping completed 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.381: 130974374793: ../libfprint/drivers/virtual-device.c:387 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.381: 130974374812: ../libfprint/drivers/virtual-device-listener.c:153 395s (process:1980): libfprint-device-DEBUG: 05:08:35.381: Device reported open completion 395s (process:1980): libfprint-device-DEBUG: 05:08:35.381: Completing action FPI_DEVICE_ACTION_OPEN in idle! 395s (process:1980): libfprint-device-DEBUG: 05:08:35.381: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.381: Got a new connection! 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.381: Got instructions of length 5 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.381: Received command CONT 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.381: Processing command CONT 395s (process:1980): libfprint-device-DEBUG: 05:08:35.382: Device reported deletion completion 395s (process:1980): libfprint-device-DEBUG: 05:08:35.382: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 395s (process:1980): libfprint-device-DEBUG: 05:08:35.382: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.382: Got a new connection! 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.382: Got instructions of length 16 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.382: Received command SET_KEEP_ALIVE 0 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.382: Keep alive toggled: 0 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.382: Got a new connection! 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.382: Got instructions of length 19 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.382: Received command SET_ENROLL_STAGES 5 395s (process:1980): libfprint-device-DEBUG: 05:08:35.382: Device reported close completion 395s (process:1980): libfprint-device-DEBUG: 05:08:35.382: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 395s (process:1980): libfprint-device-DEBUG: 05:08:35.382: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 395s ok 395s test_delayed_open_with_keep_alive (__main__.VirtualDeviceStorage.test_delayed_open_with_keep_alive) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.382: 130974376604: ../libfprint/drivers/virtual-device.c:387 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.382: 130974376624: ../libfprint/drivers/virtual-device-listener.c:153 395s (process:1980): libfprint-device-DEBUG: 05:08:35.383: Device reported open completion 395s (process:1980): libfprint-device-DEBUG: 05:08:35.383: Completing action FPI_DEVICE_ACTION_OPEN in idle! 395s (process:1980): libfprint-device-DEBUG: 05:08:35.383: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.383: Got a new connection! 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.383: Got instructions of length 16 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.383: Received command SET_KEEP_ALIVE 1 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.383: Keep alive toggled: 1 395s (process:1980): libfprint-device-DEBUG: 05:08:35.383: Device reported close completion 395s (process:1980): libfprint-device-DEBUG: 05:08:35.383: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 395s (process:1980): libfprint-device-DEBUG: 05:08:35.383: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.383: Got a new connection! 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.383: Got instructions of length 9 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.383: Received command SLEEP 500 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.383: 130974377614: ../libfprint/drivers/virtual-device.c:387 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.383: Processing command SLEEP 500 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.383: Sleeping 500ms 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.884: Sleeping completed 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.884: 130974878286: ../libfprint/drivers/virtual-device.c:387 395s (process:1980): libfprint-device-DEBUG: 05:08:35.884: Device reported open completion 395s (process:1980): libfprint-device-DEBUG: 05:08:35.884: Completing action FPI_DEVICE_ACTION_OPEN in idle! 395s (process:1980): libfprint-device-DEBUG: 05:08:35.884: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.884: Got a new connection! 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.885: Got instructions of length 5 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.885: Received command CONT 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.885: Processing command CONT 395s (process:1980): libfprint-device-DEBUG: 05:08:35.885: Device reported deletion completion 395s (process:1980): libfprint-device-DEBUG: 05:08:35.885: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 395s (process:1980): libfprint-device-DEBUG: 05:08:35.885: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.885: Got a new connection! 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.885: Got instructions of length 16 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.885: Received command SET_KEEP_ALIVE 0 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.885: Keep alive toggled: 0 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.885: Got a new connection! 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.885: Got instructions of length 19 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.885: Received command SET_ENROLL_STAGES 5 395s (process:1980): libfprint-device-DEBUG: 05:08:35.886: Device reported close completion 395s (process:1980): libfprint-device-DEBUG: 05:08:35.886: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 395s (process:1980): libfprint-device-DEBUG: 05:08:35.886: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 395s ok 395s test_delete_error (__main__.VirtualDeviceStorage.test_delete_error) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.886: 130974879970: ../libfprint/drivers/virtual-device.c:387 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.886: 130974879989: ../libfprint/drivers/virtual-device-listener.c:153 395s (process:1980): libfprint-device-DEBUG: 05:08:35.886: Device reported open completion 395s (process:1980): libfprint-device-DEBUG: 05:08:35.886: Completing action FPI_DEVICE_ACTION_OPEN in idle! 395s (process:1980): libfprint-device-DEBUG: 05:08:35.886: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.886: Got a new connection! 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.886: Got instructions of length 9 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.886: Received command SLEEP 100 395s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.887: Got a new connection! 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.887: Got instructions of length 7 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.887: Received command ERROR 7 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.887: Processing command SLEEP 100 395s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.887: Sleeping 100ms 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.987: Sleeping completed 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.987: Processing command ERROR 7 396s (process:1980): libfprint-device-DEBUG: 05:08:35.987: Device reported deletion completion 396s (process:1980): libfprint-device-DEBUG: 05:08:35.987: Completing action FPI_DEVICE_ACTION_DELETE in idle! 396s (process:1980): libfprint-device-DEBUG: 05:08:35.987: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 396s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.988: Got a new connection! 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.988: Got instructions of length 5 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.988: Received command CONT 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.988: Processing command CONT 396s (process:1980): libfprint-device-DEBUG: 05:08:35.988: Device reported deletion completion 396s (process:1980): libfprint-device-DEBUG: 05:08:35.988: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 396s (process:1980): libfprint-device-DEBUG: 05:08:35.988: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 396s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.988: Got a new connection! 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.988: Got instructions of length 16 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.988: Received command SET_KEEP_ALIVE 0 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.988: Keep alive toggled: 0 396s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.988: Got a new connection! 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.989: Got instructions of length 19 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.989: Received command SET_ENROLL_STAGES 5 396s (process:1980): libfprint-device-DEBUG: 05:08:35.989: Device reported close completion 396s (process:1980): libfprint-device-DEBUG: 05:08:35.989: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 396s (process:1980): libfprint-device-DEBUG: 05:08:35.989: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 396s ok 396s test_delete_multiple_times (__main__.VirtualDeviceStorage.test_delete_multiple_times) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.989: 130974983159: ../libfprint/drivers/virtual-device.c:387 396s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.989: 130974983183: ../libfprint/drivers/virtual-device-listener.c:153 396s (process:1980): libfprint-device-DEBUG: 05:08:35.989: Device reported open completion 396s (process:1980): libfprint-device-DEBUG: 05:08:35.989: Completing action FPI_DEVICE_ACTION_OPEN in idle! 396s (process:1980): libfprint-device-DEBUG: 05:08:35.989: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 396s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.989: Got a new connection! 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.990: Got instructions of length 16 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.990: Received command SCAN right-thumb 396s (process:1980): libfprint-device-DEBUG: 05:08:35.990: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.990: Processing command SCAN right-thumb 396s (process:1980): libfprint-device-DEBUG: 05:08:35.990: Device reported finger status change: FP_FINGER_STATUS_NEEDED 396s (process:1980): libfprint-device-DEBUG: 05:08:35.990: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 396s (process:1980): libfprint-device-DEBUG: 05:08:35.990: Device reported finger status change: FP_FINGER_STATUS_NEEDED 396s (process:1980): libfprint-device-DEBUG: 05:08:35.990: Device reported enroll progress, reported 1 of 5 have been completed 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.990: Sleeping completed 396s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.990: Got a new connection! 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.990: Got instructions of length 16 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.990: Received command SCAN right-thumb 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.990: Processing command SCAN right-thumb 396s (process:1980): libfprint-device-DEBUG: 05:08:35.990: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 396s (process:1980): libfprint-device-DEBUG: 05:08:35.990: Device reported finger status change: FP_FINGER_STATUS_NEEDED 396s (process:1980): libfprint-device-DEBUG: 05:08:35.990: Device reported enroll progress, reported 2 of 5 have been completed 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.990: Sleeping completed 396s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.991: Got a new connection! 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.991: Got instructions of length 16 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.991: Received command SCAN right-thumb 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.991: Processing command SCAN right-thumb 396s (process:1980): libfprint-device-DEBUG: 05:08:35.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 396s (process:1980): libfprint-device-DEBUG: 05:08:35.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED 396s (process:1980): libfprint-device-DEBUG: 05:08:35.991: Device reported enroll progress, reported 3 of 5 have been completed 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.991: Sleeping completed 396s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.991: Got a new connection! 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.991: Got instructions of length 16 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.991: Received command SCAN right-thumb 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.991: Processing command SCAN right-thumb 396s (process:1980): libfprint-device-DEBUG: 05:08:35.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 396s (process:1980): libfprint-device-DEBUG: 05:08:35.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED 396s (process:1980): libfprint-device-DEBUG: 05:08:35.991: Device reported enroll progress, reported 4 of 5 have been completed 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.991: Sleeping completed 396s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:35.991: Got a new connection! 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.992: Got instructions of length 16 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.992: Received command SCAN right-thumb 396s (process:1980): libfprint-virtual_device-DEBUG: 05:08:35.992: Processing command SCAN right-thumb 396s (process:1980): libfprint-device-DEBUG: 05:08:35.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 396s (process:1980): libfprint-device-DEBUG: 05:08:35.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED 396s (process:1980): libfprint-device-DEBUG: 05:08:35.992: Device reported enroll progress, reported 5 of 5 have been completed 396s (process:1980): libfprint-device-DEBUG: 05:08:35.992: Device reported enroll completion 396s (process:1980): libfprint-device-DEBUG: 05:08:35.992: Device reported finger status change: FP_FINGER_STATUS_NONE 396s (process:1980): libfprint-device-DEBUG: 05:08:35.992: Print for finger FP_FINGER_RIGHT_THUMB enrolled 396s (process:1980): libfprint-device-DEBUG: 05:08:35.992: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 396s (process:1980): libfprint-device-DEBUG: 05:08:35.992: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 396s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:36.493: Deleting print right-thumb for user testuser 396s (process:1980): libfprint-device-DEBUG: 05:08:36.493: Device reported deletion completion 396s (process:1980): libfprint-device-DEBUG: 05:08:36.493: Completing action FPI_DEVICE_ACTION_DELETE in idle! 396s (process:1980): libfprint-device-DEBUG: 05:08:36.493: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:36.993: Deleting print right-thumb for user testuser 397s (process:1980): libfprint-device-DEBUG: 05:08:36.994: Device reported deletion completion 397s (process:1980): libfprint-device-DEBUG: 05:08:36.994: Completing action FPI_DEVICE_ACTION_DELETE in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:36.994: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.994: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.994: Got instructions of length 5 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.994: Received command CONT 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.994: Processing command CONT 397s (process:1980): libfprint-device-DEBUG: 05:08:36.994: Device reported deletion completion 397s (process:1980): libfprint-device-DEBUG: 05:08:36.994: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:36.994: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.994: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.994: Got instructions of length 16 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.994: Received command SET_KEEP_ALIVE 0 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.994: Keep alive toggled: 0 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.995: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.995: Got instructions of length 19 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.995: Received command SET_ENROLL_STAGES 5 397s (process:1980): libfprint-device-DEBUG: 05:08:36.995: Device reported close completion 397s (process:1980): libfprint-device-DEBUG: 05:08:36.995: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:36.995: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s Enroll done 397s ok 397s test_device_features (__main__.VirtualDeviceStorage.test_device_features) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.995: 130975989366: ../libfprint/drivers/virtual-device.c:387 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.995: 130975989385: ../libfprint/drivers/virtual-device-listener.c:153 397s (process:1980): libfprint-device-DEBUG: 05:08:36.995: Device reported open completion 397s (process:1980): libfprint-device-DEBUG: 05:08:36.995: Completing action FPI_DEVICE_ACTION_OPEN in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:36.995: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.996: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.996: Got instructions of length 5 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.996: Received command CONT 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.996: Processing command CONT 397s (process:1980): libfprint-device-DEBUG: 05:08:36.996: Device reported deletion completion 397s (process:1980): libfprint-device-DEBUG: 05:08:36.996: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:36.996: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.996: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.996: Got instructions of length 16 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.996: Received command SET_KEEP_ALIVE 0 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.996: Keep alive toggled: 0 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.996: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.996: Got instructions of length 19 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.996: Received command SET_ENROLL_STAGES 5 397s (process:1980): libfprint-device-DEBUG: 05:08:36.996: Device reported close completion 397s (process:1980): libfprint-device-DEBUG: 05:08:36.996: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:36.996: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s ok 397s test_device_properties (__main__.VirtualDeviceStorage.test_device_properties) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.997: 130975990735: ../libfprint/drivers/virtual-device.c:387 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.997: 130975990750: ../libfprint/drivers/virtual-device-listener.c:153 397s (process:1980): libfprint-device-DEBUG: 05:08:36.997: Device reported open completion 397s (process:1980): libfprint-device-DEBUG: 05:08:36.997: Completing action FPI_DEVICE_ACTION_OPEN in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:36.997: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.997: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.997: Got instructions of length 5 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.997: Received command CONT 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.997: Processing command CONT 397s (process:1980): libfprint-device-DEBUG: 05:08:36.997: Device reported deletion completion 397s (process:1980): libfprint-device-DEBUG: 05:08:36.997: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:36.997: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.997: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.997: Got instructions of length 16 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.997: Received command SET_KEEP_ALIVE 0 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.997: Keep alive toggled: 0 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.997: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.997: Got instructions of length 19 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.997: Received command SET_ENROLL_STAGES 5 397s (process:1980): libfprint-device-DEBUG: 05:08:36.998: Device reported close completion 397s (process:1980): libfprint-device-DEBUG: 05:08:36.998: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:36.998: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s ok 397s test_device_sleep (__main__.VirtualDeviceStorage.test_device_sleep) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.998: 130975991905: ../libfprint/drivers/virtual-device.c:387 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.998: 130975991920: ../libfprint/drivers/virtual-device-listener.c:153 397s (process:1980): libfprint-device-DEBUG: 05:08:36.998: Device reported open completion 397s (process:1980): libfprint-device-DEBUG: 05:08:36.998: Completing action FPI_DEVICE_ACTION_OPEN in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:36.998: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:36.998: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.998: Got instructions of length 10 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.998: Received command SLEEP 1500 397s (process:1980): libfprint-device-DEBUG: 05:08:36.998: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.998: Processing command SLEEP 1500 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:36.998: Sleeping 1500ms 397s (process:1980): libfprint-device-DEBUG: 05:08:37.299: Idle cancelling on ongoing operation! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.299: Got cancellation! 397s (process:1980): libfprint-device-DEBUG: 05:08:37.299: Device reported finger status change: FP_FINGER_STATUS_NEEDED 397s (process:1980): libfprint-device-DEBUG: 05:08:37.299: Device reported identify completion 397s (process:1980): libfprint-device-DEBUG: 05:08:37.299: Device reported finger status change: FP_FINGER_STATUS_NONE 397s (process:1980): libfprint-device-DEBUG: 05:08:37.299: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:37.299: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.499: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.499: Got instructions of length 5 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.499: Received command CONT 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.499: Processing command CONT 397s (process:1980): libfprint-device-DEBUG: 05:08:37.499: Device reported deletion completion 397s (process:1980): libfprint-device-DEBUG: 05:08:37.499: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:37.499: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.499: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.499: Got instructions of length 16 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.499: Received command SET_KEEP_ALIVE 0 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.499: Keep alive toggled: 0 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.500: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.500: Got instructions of length 19 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.500: Received command SET_ENROLL_STAGES 5 397s (process:1980): libfprint-device-DEBUG: 05:08:37.500: Device reported close completion 397s (process:1980): libfprint-device-DEBUG: 05:08:37.500: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:37.500: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s ok 397s test_device_sleep_before_completing_verify (__main__.VirtualDeviceStorage.test_device_sleep_before_completing_verify) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.500: 130976494213: ../libfprint/drivers/virtual-device.c:387 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.500: 130976494230: ../libfprint/drivers/virtual-device-listener.c:153 397s (process:1980): libfprint-device-DEBUG: 05:08:37.500: Device reported open completion 397s (process:1980): libfprint-device-DEBUG: 05:08:37.500: Completing action FPI_DEVICE_ACTION_OPEN in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:37.500: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.501: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.501: Got instructions of length 14 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.501: Received command SCAN foo-print 397s (process:1980): libfprint-device-DEBUG: 05:08:37.501: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.501: Processing command SCAN foo-print 397s (process:1980): libfprint-device-DEBUG: 05:08:37.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED 397s (process:1980): libfprint-device-DEBUG: 05:08:37.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 397s (process:1980): libfprint-device-DEBUG: 05:08:37.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED 397s (process:1980): libfprint-device-DEBUG: 05:08:37.501: Device reported enroll progress, reported 1 of 5 have been completed 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.501: Sleeping completed 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.501: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.501: Got instructions of length 14 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.501: Received command SCAN foo-print 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.501: Processing command SCAN foo-print 397s (process:1980): libfprint-device-DEBUG: 05:08:37.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 397s (process:1980): libfprint-device-DEBUG: 05:08:37.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED 397s (process:1980): libfprint-device-DEBUG: 05:08:37.501: Device reported enroll progress, reported 2 of 5 have been completed 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.502: Sleeping completed 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.502: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.502: Got instructions of length 14 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.502: Received command SCAN foo-print 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.502: Processing command SCAN foo-print 397s (process:1980): libfprint-device-DEBUG: 05:08:37.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 397s (process:1980): libfprint-device-DEBUG: 05:08:37.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED 397s (process:1980): libfprint-device-DEBUG: 05:08:37.502: Device reported enroll progress, reported 3 of 5 have been completed 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.502: Sleeping completed 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.502: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.502: Got instructions of length 14 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.502: Received command SCAN foo-print 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.502: Processing command SCAN foo-print 397s (process:1980): libfprint-device-DEBUG: 05:08:37.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 397s (process:1980): libfprint-device-DEBUG: 05:08:37.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED 397s (process:1980): libfprint-device-DEBUG: 05:08:37.502: Device reported enroll progress, reported 4 of 5 have been completed 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.503: Sleeping completed 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.503: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.503: Got instructions of length 14 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.503: Received command SCAN foo-print 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.503: Processing command SCAN foo-print 397s (process:1980): libfprint-device-DEBUG: 05:08:37.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 397s (process:1980): libfprint-device-DEBUG: 05:08:37.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED 397s (process:1980): libfprint-device-DEBUG: 05:08:37.503: Device reported enroll progress, reported 5 of 5 have been completed 397s (process:1980): libfprint-device-DEBUG: 05:08:37.503: Device reported enroll completion 397s (process:1980): libfprint-device-DEBUG: 05:08:37.503: Device reported finger status change: FP_FINGER_STATUS_NONE 397s (process:1980): libfprint-device-DEBUG: 05:08:37.503: Print for finger FP_FINGER_LEFT_RING enrolled 397s (process:1980): libfprint-device-DEBUG: 05:08:37.503: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 397s (process:1980): libfprint-device-DEBUG: 05:08:37.503: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.503: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.503: Got instructions of length 9 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.503: Received command SLEEP 100 397s (process:1980): libfprint-device-DEBUG: 05:08:37.504: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.504: Processing command SLEEP 100 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.504: Sleeping 100ms 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.504: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.504: Got instructions of length 14 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.504: Received command SCAN bar-print 397s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:37.504: Got a new connection! 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.504: Got instructions of length 9 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.504: Received command SLEEP 800 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.604: Sleeping completed 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.604: Processing command SCAN bar-print 397s (process:1980): libfprint-device-DEBUG: 05:08:37.604: Device reported finger status change: FP_FINGER_STATUS_NEEDED 397s (process:1980): libfprint-device-DEBUG: 05:08:37.604: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 397s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:37.604: Trying to identify print 'bar-print' against a gallery of 1 prints 397s (process:1980): libfprint-device-DEBUG: 05:08:37.604: Device reported identify result 397s (process:1980): libfprint-device-DEBUG: 05:08:37.604: Device reported finger status change: FP_FINGER_STATUS_NEEDED 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.604: Processing command SLEEP 800 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.604: Sleeping 800ms 397s (process:1980): libfprint-virtual_device-DEBUG: 05:08:37.604: Sleeping now, command queued for later: SCAN bar-print 397s (process:1980): libfprint-device-DEBUG: 05:08:37.842: Updated temperature model after 0.34 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 397s Executing: libfprint-2/virtual-device.test 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.405: Sleeping completed 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.405: Processing command SCAN bar-print 398s (process:1980): libfprint-device-DEBUG: 05:08:38.405: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 398s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:38.405: Trying to identify print 'bar-print' against a gallery of 1 prints 398s (process:1980): libfprint-device-DEBUG: 05:08:38.405: Device reported finger status change: FP_FINGER_STATUS_NEEDED 398s (process:1980): libfprint-device-DEBUG: 05:08:38.405: Device reported identify completion 398s (process:1980): libfprint-device-DEBUG: 05:08:38.405: Device reported finger status change: FP_FINGER_STATUS_NONE 398s (process:1980): libfprint-device-DEBUG: 05:08:38.405: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 398s (process:1980): libfprint-device-DEBUG: 05:08:38.405: Updated temperature model after 0.56 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 398s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:38.405: Got a new connection! 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.405: Got instructions of length 5 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.405: Received command CONT 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.405: Processing command CONT 398s (process:1980): libfprint-device-DEBUG: 05:08:38.405: Device reported deletion completion 398s (process:1980): libfprint-device-DEBUG: 05:08:38.405: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 398s (process:1980): libfprint-device-DEBUG: 05:08:38.405: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 398s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:38.406: Got a new connection! 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.406: Got instructions of length 16 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.406: Received command SET_KEEP_ALIVE 0 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.406: Keep alive toggled: 0 398s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:38.406: Got a new connection! 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.406: Got instructions of length 19 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.406: Received command SET_ENROLL_STAGES 5 398s (process:1980): libfprint-device-DEBUG: 05:08:38.406: Device reported close completion 398s (process:1980): libfprint-device-DEBUG: 05:08:38.406: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 398s (process:1980): libfprint-device-DEBUG: 05:08:38.406: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 398s Enroll done 398s ok 398s test_device_sleep_on_cancellation (__main__.VirtualDeviceStorage.test_device_sleep_on_cancellation) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.406: 130977400501: ../libfprint/drivers/virtual-device.c:387 398s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:38.406: 130977400528: ../libfprint/drivers/virtual-device-listener.c:153 398s (process:1980): libfprint-device-DEBUG: 05:08:38.406: Device reported open completion 398s (process:1980): libfprint-device-DEBUG: 05:08:38.407: Completing action FPI_DEVICE_ACTION_OPEN in idle! 398s (process:1980): libfprint-device-DEBUG: 05:08:38.407: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 398s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:38.407: Got a new connection! 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.407: Got instructions of length 26 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.407: Received command SET_CANCELLATION_ENABLED 0 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.407: Cancellation support toggled: 0 398s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:38.407: Got a new connection! 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.407: Got instructions of length 10 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.407: Received command SLEEP 1500 398s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:38.407: Got a new connection! 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.407: Got instructions of length 14 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.407: Received command SCAN foo-print 398s (process:1980): libfprint-device-DEBUG: 05:08:38.408: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.408: Processing command SLEEP 1500 398s (process:1980): libfprint-virtual_device-DEBUG: 05:08:38.408: Sleeping 1500ms 398s (process:1980): libfprint-device-DEBUG: 05:08:38.708: Idle cancelling on ongoing operation! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.909: Sleeping completed 399s (process:1980): libfprint-device-DEBUG: 05:08:39.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.909: Device reported identify completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.909: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:1980): libfprint-device-DEBUG: 05:08:39.909: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.909: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.909: Processing command SCAN foo-print 399s (process:1980): libfprint-device-DEBUG: 05:08:39.909: Device reported close completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.909: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.909: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s ok 399s test_duplicate_enroll (__main__.VirtualDeviceStorage.test_duplicate_enroll) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.910: 130978903773: ../libfprint/drivers/virtual-device.c:387 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.910: 130978903793: ../libfprint/drivers/virtual-device-listener.c:153 399s (process:1980): libfprint-device-DEBUG: 05:08:39.910: Device reported open completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.910: Completing action FPI_DEVICE_ACTION_OPEN in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.910: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.910: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.910: Got instructions of length 14 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.910: Received command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.910: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.910: Processing command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.910: Device reported enroll progress, reported 1 of 5 have been completed 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.911: Sleeping completed 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.911: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.911: Got instructions of length 14 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.911: Received command SCAN testprint 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.911: Processing command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.911: Device reported enroll progress, reported 2 of 5 have been completed 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.911: Sleeping completed 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.911: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.911: Got instructions of length 14 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.911: Received command SCAN testprint 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.911: Processing command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.911: Device reported enroll progress, reported 3 of 5 have been completed 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.911: Sleeping completed 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.911: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.912: Got instructions of length 14 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.912: Received command SCAN testprint 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.912: Processing command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Device reported enroll progress, reported 4 of 5 have been completed 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.912: Sleeping completed 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.912: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.912: Got instructions of length 14 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.912: Received command SCAN testprint 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.912: Processing command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Device reported enroll progress, reported 5 of 5 have been completed 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Device reported enroll completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Print for finger FP_FINGER_LEFT_LITTLE enrolled 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.912: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.912: Got instructions of length 14 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.912: Received command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.912: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.913: Processing command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Device reported enroll completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.913: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.913: Got instructions of length 5 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.913: Received command CONT 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.913: Processing command CONT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Device reported deletion completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.913: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.913: Got instructions of length 16 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.913: Received command SET_KEEP_ALIVE 0 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.913: Keep alive toggled: 0 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.913: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.913: Got instructions of length 19 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.913: Received command SET_ENROLL_STAGES 5 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Device reported close completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s Enroll done 399s Enroll done 399s ok 399s test_enroll (__main__.VirtualDeviceStorage.test_enroll) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.914: 130978907828: ../libfprint/drivers/virtual-device.c:387 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.914: 130978907846: ../libfprint/drivers/virtual-device-listener.c:153 399s (process:1980): libfprint-device-DEBUG: 05:08:39.914: Device reported open completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.914: Completing action FPI_DEVICE_ACTION_OPEN in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.914: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.914: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.914: Got instructions of length 14 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.914: Received command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.914: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.914: Processing command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.914: Device reported enroll progress, reported 1 of 5 have been completed 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.914: Sleeping completed 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.914: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.914: Got instructions of length 14 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.914: Received command SCAN testprint 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.914: Processing command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported enroll progress, reported 2 of 5 have been completed 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Sleeping completed 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.915: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Got instructions of length 14 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Received command SCAN testprint 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Processing command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported enroll progress, reported 3 of 5 have been completed 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Sleeping completed 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.915: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Got instructions of length 14 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Received command SCAN testprint 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Processing command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported enroll progress, reported 4 of 5 have been completed 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Sleeping completed 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.915: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Got instructions of length 14 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Received command SCAN testprint 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.915: Processing command SCAN testprint 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported enroll progress, reported 5 of 5 have been completed 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported enroll completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Device reported finger status change: FP_FINGER_STATUS_NONE 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Print for finger FP_FINGER_LEFT_LITTLE enrolled 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.915: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.916: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.916: Got instructions of length 5 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.916: Received command CONT 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.916: Processing command CONT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.916: Device reported deletion completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.916: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.916: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.916: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.916: Got instructions of length 16 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.916: Received command SET_KEEP_ALIVE 0 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.916: Keep alive toggled: 0 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.916: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.916: Got instructions of length 19 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.916: Received command SET_ENROLL_STAGES 5 399s (process:1980): libfprint-device-DEBUG: 05:08:39.916: Device reported close completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.916: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.916: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s Enroll done 399s ok 399s test_enroll_script (__main__.VirtualDeviceStorage.test_enroll_script) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.917: 130978910797: ../libfprint/drivers/virtual-device.c:387 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.917: 130978910812: ../libfprint/drivers/virtual-device-listener.c:153 399s (process:1980): libfprint-device-DEBUG: 05:08:39.917: Device reported open completion 399s (process:1980): libfprint-device-DEBUG: 05:08:39.917: Completing action FPI_DEVICE_ACTION_OPEN in idle! 399s (process:1980): libfprint-device-DEBUG: 05:08:39.917: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.917: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.917: Got instructions of length 19 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.917: Received command SET_ENROLL_STAGES 8 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.917: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.917: Got instructions of length 13 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.917: Received command SCAN print-id 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.917: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.917: Got instructions of length 13 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.917: Received command SCAN print-id 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.918: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Got instructions of length 7 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Received command RETRY 1 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.918: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Got instructions of length 13 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Received command SCAN print-id 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.918: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Got instructions of length 7 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Received command RETRY 3 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.918: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Got instructions of length 13 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Received command SCAN print-id 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.918: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Got instructions of length 7 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Received command RETRY 2 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.918: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Got instructions of length 13 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.918: Received command SCAN print-id 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.919: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Got instructions of length 8 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Received command SLEEP 10 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.919: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Got instructions of length 8 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Received command SLEEP 20 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.919: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Got instructions of length 7 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Received command RETRY 0 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.919: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Got instructions of length 7 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Received command RETRY 3 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.919: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Got instructions of length 13 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Received command SCAN print-id 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.919: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Got instructions of length 15 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.919: Received command SCAN another-id 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.920: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Got instructions of length 13 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Received command SCAN print-id 399s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.920: Got a new connection! 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Got instructions of length 13 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Received command SCAN print-id 399s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Processing command SCAN print-id 399s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported enroll progress, reported 1 of 8 have been completed 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Sleeping completed 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Processing command SCAN print-id 399s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 399s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED 399s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported enroll progress, reported 2 of 8 have been completed 399s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Processing command RETRY 1 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported enroll progress, reported 2 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported enroll progress, reported 3 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Processing command RETRY 3 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported enroll progress, reported 3 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported enroll progress, reported 4 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Processing command RETRY 2 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported enroll progress, reported 4 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:39.920: Device reported enroll progress, reported 5 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Processing command SLEEP 10 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.920: Sleeping 10ms 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.930: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.930: Processing command SLEEP 20 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.930: Sleeping 20ms 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.950: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.950: Processing command RETRY 0 400s (process:1980): libfprint-device-DEBUG: 05:08:39.950: Device reported enroll progress, reported 5 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.950: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.950: Processing command RETRY 3 400s (process:1980): libfprint-device-DEBUG: 05:08:39.950: Device reported enroll progress, reported 5 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.950: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.950: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:39.950: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported enroll progress, reported 6 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Processing command SCAN another-id 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported enroll progress, reported 6 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported enroll progress, reported 7 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported enroll progress, reported 8 of 8 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Print for finger FP_FINGER_UNKNOWN enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.951: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:39.951: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.951: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.951: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.952: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.952: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.952: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:39.952: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:39.952: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:39.952: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s ok 400s test_enroll_script_interactive (__main__.VirtualDeviceStorage.test_enroll_script_interactive) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.952: 130978946184: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.952: 130978946201: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:39.952: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:39.952: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:39.952: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.952: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.952: Got instructions of length 8 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.952: Received command SLEEP 50 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.953: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.953: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.953: Received command SCAN print-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.953: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.953: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.953: Received command SCAN print-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.953: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.953: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.953: Received command RETRY 1 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.953: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.953: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.953: Received command SCAN print-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.953: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.953: Got instructions of length 8 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.953: Received command SLEEP 50 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.953: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.954: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.954: Received command SCAN print-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.954: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.954: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.954: Received command RETRY 2 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.954: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.954: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.954: Received command SCAN another-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:39.954: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.954: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.954: Received command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:39.954: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.954: Processing command SLEEP 50 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:39.954: Sleeping 50ms 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.004: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.004: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.005: Device reported enroll progress, reported 1 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.005: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.005: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.005: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.005: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.005: Processing command RETRY 1 400s (process:1980): libfprint-device-DEBUG: 05:08:40.005: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.005: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.005: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.005: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.005: Device reported enroll progress, reported 3 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.005: Processing command SLEEP 50 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.005: Sleeping 50ms 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.055: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.055: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.055: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.055: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.055: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.055: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.055: Processing command RETRY 2 400s (process:1980): libfprint-device-DEBUG: 05:08:40.055: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.055: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.055: Processing command SCAN another-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.055: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.055: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.055: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.055: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.055: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.055: Device reported enroll progress, reported 5 of 5 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.055: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.055: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.055: Print for finger FP_FINGER_UNKNOWN enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:40.056: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.056: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.056: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.056: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.056: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.056: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.056: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.056: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.056: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.056: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.056: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.056: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.056: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.057: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.057: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.057: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.057: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.057: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.057: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s ok 400s test_enroll_verify_error (__main__.VirtualDeviceStorage.test_enroll_verify_error) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.057: 130979051340: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.057: 130979051360: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.057: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.057: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.057: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.058: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.058: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.058: Received command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.058: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.058: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.058: Device reported enroll progress, reported 1 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.058: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.058: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.058: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.058: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.058: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.058: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.058: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.059: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.059: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.059: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.059: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Device reported enroll progress, reported 3 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.059: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.059: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.059: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.059: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.059: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.059: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.059: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.059: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.059: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.059: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Device reported enroll progress, reported 5 of 5 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.059: Print for finger FP_FINGER_LEFT_RING enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:40.060: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.060: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.060: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.060: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.060: Received command ERROR 0 400s (process:1980): libfprint-device-DEBUG: 05:08:40.060: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.060: Processing command ERROR 0 400s (process:1980): libfprint-device-DEBUG: 05:08:40.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.060: Device reported identify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.060: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.060: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.060: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.060: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.060: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.060: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.060: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.060: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.060: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.060: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.061: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.061: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.061: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.061: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.061: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.061: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.061: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.061: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.061: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.061: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s Enroll done 400s ok 400s test_enroll_verify_match (__main__.VirtualDeviceStorage.test_enroll_verify_match) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.061: 130979055282: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.061: 130979055301: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.061: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.061: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.061: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.061: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Received command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.062: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.062: Device reported enroll progress, reported 1 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.062: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.062: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.062: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.062: Device reported enroll progress, reported 3 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.062: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.062: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.063: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.063: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.063: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.063: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.063: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.063: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.063: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.063: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Device reported enroll progress, reported 5 of 5 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Print for finger FP_FINGER_LEFT_THUMB enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.063: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.063: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.063: Received command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.063: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:40.063: Trying to identify print 'testprint' against a gallery of 1 prints 400s (process:1980): libfprint-device-DEBUG: 05:08:40.063: Device reported identify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.064: Device reported identify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.064: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.064: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.064: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.064: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.064: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.064: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.064: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.064: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.064: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.064: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.064: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.064: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.064: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.064: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.064: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.064: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.064: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.064: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.064: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.064: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s Enroll done 400s ok 400s test_enroll_verify_no_match (__main__.VirtualDeviceStorage.test_enroll_verify_no_match) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.065: 130979058765: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.065: 130979058781: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.065: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.065: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.065: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.065: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.065: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.065: Received command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.065: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.065: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.065: Device reported enroll progress, reported 1 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.065: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.065: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.065: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.065: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.065: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.065: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.066: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Device reported enroll progress, reported 3 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.066: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.066: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.066: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Device reported enroll progress, reported 5 of 5 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.066: Print for finger FP_FINGER_LEFT_RING enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.067: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.067: Got instructions of length 18 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.067: Received command SCAN not-testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.067: Processing command SCAN not-testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:40.067: Trying to identify print 'not-testprint' against a gallery of 1 prints 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Device reported identify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Device reported identify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.067: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.067: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.067: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.067: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.067: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.068: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.068: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.068: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.068: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.068: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.068: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.068: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.068: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.068: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s Enroll done 400s ok 400s test_enroll_verify_retry (__main__.VirtualDeviceStorage.test_enroll_verify_retry) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.068: 130979062328: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.068: 130979062346: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.068: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.068: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.068: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Received command RETRY 1 400s (process:1980): libfprint-device-DEBUG: 05:08:40.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Processing command RETRY 1 400s (process:1980): libfprint-device-DEBUG: 05:08:40.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Virtual device scan failed with error: The swipe was too short, please try again. 400s (process:1980): libfprint-device-DEBUG: 05:08:40.069: Device reported verify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.069: Device reported verify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.069: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.069: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.069: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.069: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.069: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.069: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.069: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.069: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.070: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.070: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.070: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s ok 400s test_enroll_verify_script (__main__.VirtualDeviceStorage.test_enroll_verify_script) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.070: 130979063950: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.070: 130979063989: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.070: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.070: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.070: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.070: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.070: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.070: Received command SET_ENROLL_STAGES 8 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.070: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.070: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.070: Received command SCAN print-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.071: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.071: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.071: Received command SCAN print-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.071: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.071: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.071: Received command RETRY 1 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.071: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.071: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.071: Received command SCAN print-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.071: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.071: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.071: Received command RETRY 3 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.071: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.071: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.071: Received command SCAN print-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.072: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.072: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.072: Received command RETRY 2 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.072: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.072: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.072: Received command SCAN print-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.072: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.072: Got instructions of length 8 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.072: Received command SLEEP 10 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.072: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.072: Got instructions of length 8 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.072: Received command SLEEP 20 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.072: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.072: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.072: Received command RETRY 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.072: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Received command RETRY 3 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.073: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Received command SCAN print-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.073: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Received command SCAN another-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.073: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Received command SCAN print-id 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.073: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Received command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Device reported enroll progress, reported 1 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Device reported enroll progress, reported 2 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Processing command RETRY 1 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Device reported enroll progress, reported 2 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.073: Device reported enroll progress, reported 3 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.073: Processing command RETRY 3 400s (process:1980): libfprint-device-DEBUG: 05:08:40.074: Device reported enroll progress, reported 3 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.074: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.074: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.074: Device reported enroll progress, reported 4 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.074: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.074: Processing command RETRY 2 400s (process:1980): libfprint-device-DEBUG: 05:08:40.074: Device reported enroll progress, reported 4 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.074: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.074: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.074: Device reported enroll progress, reported 5 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.074: Processing command SLEEP 10 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.074: Sleeping 10ms 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.084: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.084: Processing command SLEEP 20 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.084: Sleeping 20ms 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Processing command RETRY 0 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported enroll progress, reported 5 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Processing command RETRY 3 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported enroll progress, reported 5 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported enroll progress, reported 6 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Processing command SCAN another-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported enroll progress, reported 6 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported enroll progress, reported 7 of 8 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.104: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported enroll progress, reported 8 of 8 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Print for finger FP_FINGER_UNKNOWN enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.104: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.105: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.105: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.105: Received command RETRY 2 400s (process:1980): libfprint-device-DEBUG: 05:08:40.105: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.105: Processing command RETRY 2 400s (process:1980): libfprint-device-DEBUG: 05:08:40.105: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.105: Virtual device scan failed with error: The finger was not centered properly, please try again. 400s (process:1980): libfprint-device-DEBUG: 05:08:40.105: Device reported verify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.105: Device reported verify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.105: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.105: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.105: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.105: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.105: Got instructions of length 8 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.105: Received command SLEEP 50 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.105: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.105: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.105: Received command RETRY 1 400s (process:1980): libfprint-device-DEBUG: 05:08:40.105: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.105: Processing command SLEEP 50 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.105: Sleeping 50ms 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.156: Sleeping completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.156: Processing command RETRY 1 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.156: Virtual device scan failed with error: The swipe was too short, please try again. 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Device reported verify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Device reported verify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.156: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.156: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.156: Received command SCAN another-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.156: Processing command SCAN another-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.156: Virtual device scanned print another-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Device reported verify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Device reported verify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.156: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.157: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.157: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.157: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.157: Got instructions of length 13 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.157: Received command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.157: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.157: Processing command SCAN print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.157: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.157: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.157: Virtual device scanned print print-id 400s (process:1980): libfprint-device-DEBUG: 05:08:40.157: Device reported verify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.157: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.157: Device reported verify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.157: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.157: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.157: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.157: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.158: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.158: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.158: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.158: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.158: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.158: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.158: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.158: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.158: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.158: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.158: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.158: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.158: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.158: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.158: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.158: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s ok 400s test_enroll_with_retry (__main__.VirtualDeviceStorage.test_enroll_with_retry) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.159: 130979152769: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.159: 130979152797: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.159: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.159: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.159: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.159: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.159: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.159: Received command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.159: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.159: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.159: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.159: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.159: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.159: Device reported enroll progress, reported 1 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.159: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.160: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.160: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.160: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.160: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.160: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.160: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.160: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.160: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.160: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.160: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.160: Received command RETRY 1 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.160: Processing command RETRY 1 400s (process:1980): libfprint-device-DEBUG: 05:08:40.160: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.160: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.160: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.160: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.161: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.161: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Device reported enroll progress, reported 3 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.161: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.161: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.161: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.161: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.161: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.161: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.161: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.161: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.161: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.161: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Device reported enroll progress, reported 5 of 5 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Print for finger FP_FINGER_LEFT_LITTLE enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.161: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.162: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.162: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.162: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.162: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.162: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.162: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.162: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.162: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.162: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.162: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.162: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.162: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.162: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.162: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.162: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.162: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.162: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s Enroll done 400s ok 400s test_finger_status (__main__.VirtualDeviceStorage.test_finger_status) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.162: 130979156577: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.162: 130979156595: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.163: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.163: Got instructions of length 8 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.163: Received command FINGER 1 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.163: Processing command FINGER 1 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.163: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.163: Got instructions of length 8 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.163: Received command FINGER 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.163: Processing command FINGER 0 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Idle cancelling on ongoing operation! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.163: Got cancellation! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Device reported identify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.163: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.164: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.164: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.164: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.164: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.164: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.164: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.164: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.164: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.164: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.164: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.164: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.164: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.164: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.164: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.164: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.164: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.164: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s ok 400s test_finger_status_after_sleep (__main__.VirtualDeviceStorage.test_finger_status_after_sleep) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.164: 130979158608: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.164: 130979158624: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.165: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.165: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.165: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.165: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.165: Got instructions of length 8 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.165: Received command SLEEP 10 400s (process:1980): libfprint-device-DEBUG: 05:08:40.165: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.165: Processing command SLEEP 10 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.165: Sleeping 10ms 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.175: Sleeping completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.175: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.175: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.176: Got instructions of length 8 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.176: Received command FINGER 1 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.176: Processing command FINGER 1 400s (process:1980): libfprint-device-DEBUG: 05:08:40.176: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.176: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.176: Got instructions of length 8 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.176: Received command FINGER 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.176: Processing command FINGER 0 400s (process:1980): libfprint-device-DEBUG: 05:08:40.176: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.176: Idle cancelling on ongoing operation! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.176: Got cancellation! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.176: Device reported identify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.176: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.176: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.176: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.176: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.176: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.176: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.176: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.176: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.176: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.177: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.177: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.177: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.177: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.177: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.177: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.177: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.177: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.177: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.177: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.177: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s ok 400s test_identify_match (__main__.VirtualDeviceStorage.test_identify_match) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.177: 130979171627: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.177: 130979171658: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.178: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.178: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.178: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.178: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.178: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.178: Received command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.178: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.178: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.178: Device reported enroll progress, reported 1 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.178: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.178: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Received command SCAN right-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.179: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.179: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Received command SCAN right-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.179: Device reported enroll progress, reported 3 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.179: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Received command SCAN right-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.179: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.179: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.179: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.180: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.180: Received command SCAN right-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.180: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported enroll progress, reported 5 of 5 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Print for finger FP_FINGER_RIGHT_THUMB enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.180: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.180: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.180: Received command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.180: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported enroll progress, reported 1 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.180: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.180: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.180: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.180: Received command SCAN left-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.180: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.180: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.181: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Received command SCAN left-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Device reported enroll progress, reported 3 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.181: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Received command SCAN left-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.181: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Received command SCAN left-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.181: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Device reported enroll progress, reported 5 of 5 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Print for finger FP_FINGER_LEFT_THUMB enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:40.181: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.182: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.182: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.182: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.182: Received command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.182: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.182: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:40.182: Trying to identify print 'right-thumb' against a gallery of 2 prints 400s (process:1980): libfprint-device-DEBUG: 05:08:40.182: Device reported identify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.182: Device reported identify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.182: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.182: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.182: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.182: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.182: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.182: Received command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.183: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:40.183: Trying to identify print 'left-thumb' against a gallery of 2 prints 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Device reported identify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Device reported identify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.183: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.183: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.183: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.183: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.183: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.183: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.183: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.183: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.183: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.183: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.183: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.183: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s Enroll done 400s Enroll done 400s ok 400s test_identify_missing_print (__main__.VirtualDeviceStorage.test_identify_missing_print) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.184: 130979177824: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.184: 130979177839: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.184: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.184: Got instructions of length 23 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.184: Received command SCAN not-existing-print 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.184: Processing command SCAN not-existing-print 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:40.184: Trying to identify print 'not-existing-print' against a gallery of 1 prints 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Device reported identify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Device reported identify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.184: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.184: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.185: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.185: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.185: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.185: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.185: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.185: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.185: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.185: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.185: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.185: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.185: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.185: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.185: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.185: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.185: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.185: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s ok 400s test_identify_no_match (__main__.VirtualDeviceStorage.test_identify_no_match) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.185: 130979179620: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.185: 130979179634: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.186: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.186: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.186: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.186: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.186: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.186: Received command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.186: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.186: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.186: Device reported enroll progress, reported 1 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.186: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.186: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.186: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.186: Received command SCAN right-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.186: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.186: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.187: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.187: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.187: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.187: Received command SCAN right-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.187: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.187: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.187: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.187: Device reported enroll progress, reported 3 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.187: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.187: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.187: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.187: Received command SCAN right-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.187: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.187: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.187: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.187: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.187: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.188: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.188: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.188: Received command SCAN right-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.188: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Device reported enroll progress, reported 5 of 5 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Print for finger FP_FINGER_RIGHT_THUMB enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.188: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.188: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.188: Received command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.188: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.188: Device reported enroll progress, reported 1 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.188: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.188: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Received command SCAN left-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.189: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.189: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Received command SCAN left-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.189: Device reported enroll progress, reported 3 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.189: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Received command SCAN left-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.189: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.189: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.190: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.190: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.190: Received command SCAN left-thumb 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.190: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Device reported enroll progress, reported 5 of 5 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Print for finger FP_FINGER_LEFT_THUMB enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.190: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.190: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.190: Received command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.190: Processing command SCAN right-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:40.190: Trying to identify print 'right-thumb' against a gallery of 1 prints 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Device reported identify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Device reported identify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.190: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.190: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.190: Got instructions of length 15 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.190: Received command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.191: Processing command SCAN left-thumb 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:40.191: Trying to identify print 'left-thumb' against a gallery of 1 prints 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Device reported identify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Device reported identify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.191: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.191: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.191: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.191: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.191: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.191: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.191: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.191: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.191: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.191: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.191: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.191: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s Enroll done 400s Enroll done 400s ok 400s test_identify_retry (__main__.VirtualDeviceStorage.test_identify_retry) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.192: 130979185919: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.192: 130979185935: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.192: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.192: Got instructions of length 7 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.192: Received command RETRY 1 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.192: Processing command RETRY 1 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Device reported identify result 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Device reported identify completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.193: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.193: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.193: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.193: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.193: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.193: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.193: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.193: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.193: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.193: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.193: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.193: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.193: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.193: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.193: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.193: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.193: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s ok 400s test_identify_unsupported (__main__.VirtualDeviceStorage.test_identify_unsupported) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.193: 130979187581: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.193: 130979187601: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.194: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.194: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.194: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s skipped 'Device supports identification' 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.194: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.194: Got instructions of length 5 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.194: Received command CONT 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.194: Processing command CONT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.194: Device reported deletion completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.194: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.194: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.194: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.194: Got instructions of length 16 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.194: Received command SET_KEEP_ALIVE 0 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.194: Keep alive toggled: 0 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.194: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.194: Got instructions of length 19 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.194: Received command SET_ENROLL_STAGES 5 400s (process:1980): libfprint-device-DEBUG: 05:08:40.194: Device reported close completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.194: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.194: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s test_list_delete (__main__.VirtualDeviceStorage.test_list_delete) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.195: 130979188749: ../libfprint/drivers/virtual-device.c:387 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.195: 130979188765: ../libfprint/drivers/virtual-device-listener.c:153 400s (process:1980): libfprint-device-DEBUG: 05:08:40.195: Device reported open completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.195: Completing action FPI_DEVICE_ACTION_OPEN in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.195: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.195: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.195: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.195: Received command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.195: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.195: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.195: Device reported enroll progress, reported 1 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.195: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.195: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.195: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.195: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.195: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.195: Device reported enroll progress, reported 2 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.195: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.196: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.196: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.196: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.196: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Device reported enroll progress, reported 3 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.196: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.196: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.196: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.196: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.196: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Device reported enroll progress, reported 4 of 5 have been completed 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.196: Sleeping completed 400s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:40.196: Got a new connection! 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.196: Got instructions of length 14 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.196: Received command SCAN testprint 400s (process:1980): libfprint-virtual_device-DEBUG: 05:08:40.196: Processing command SCAN testprint 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Device reported enroll progress, reported 5 of 5 have been completed 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Device reported enroll completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Device reported finger status change: FP_FINGER_STATUS_NONE 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Print for finger FP_FINGER_RIGHT_THUMB enrolled 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.196: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 400s (process:1980): libfprint-device-DEBUG: 05:08:40.697: Device reported listing completion 400s (process:1980): libfprint-device-DEBUG: 05:08:40.697: Completing action FPI_DEVICE_ACTION_LIST in idle! 400s (process:1980): libfprint-device-DEBUG: 05:08:40.697: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 401s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:41.198: Deleting print testprint for user testuser 401s (process:1980): libfprint-device-DEBUG: 05:08:41.198: Device reported deletion completion 401s (process:1980): libfprint-device-DEBUG: 05:08:41.198: Completing action FPI_DEVICE_ACTION_DELETE in idle! 401s (process:1980): libfprint-device-DEBUG: 05:08:41.198: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 401s (process:1980): libfprint-device-DEBUG: 05:08:41.699: Device reported listing completion 401s (process:1980): libfprint-device-DEBUG: 05:08:41.699: Completing action FPI_DEVICE_ACTION_LIST in idle! 401s (process:1980): libfprint-device-DEBUG: 05:08:41.699: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 401s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:41.699: Got a new connection! 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.699: Got instructions of length 5 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.699: Received command CONT 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.699: Processing command CONT 401s (process:1980): libfprint-device-DEBUG: 05:08:41.699: Device reported deletion completion 401s (process:1980): libfprint-device-DEBUG: 05:08:41.700: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 401s (process:1980): libfprint-device-DEBUG: 05:08:41.700: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 401s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:41.700: Got a new connection! 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.700: Got instructions of length 16 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.700: Received command SET_KEEP_ALIVE 0 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.700: Keep alive toggled: 0 401s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:41.700: Got a new connection! 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.700: Got instructions of length 19 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.700: Received command SET_ENROLL_STAGES 5 401s (process:1980): libfprint-device-DEBUG: 05:08:41.700: Device reported close completion 401s (process:1980): libfprint-device-DEBUG: 05:08:41.700: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 401s (process:1980): libfprint-device-DEBUG: 05:08:41.700: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 401s Enroll done 401s 401s blub 'testprint' 401s ok 401s test_list_delete_missing (__main__.VirtualDeviceStorage.test_list_delete_missing) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.701: 130980694795: ../libfprint/drivers/virtual-device.c:387 401s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:41.701: 130980694819: ../libfprint/drivers/virtual-device-listener.c:153 401s (process:1980): libfprint-device-DEBUG: 05:08:41.701: Device reported open completion 401s (process:1980): libfprint-device-DEBUG: 05:08:41.701: Completing action FPI_DEVICE_ACTION_OPEN in idle! 401s (process:1980): libfprint-device-DEBUG: 05:08:41.701: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 401s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:41.701: Got a new connection! 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.701: Got instructions of length 14 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.701: Received command SCAN testprint 401s (process:1980): libfprint-device-DEBUG: 05:08:41.701: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.701: Processing command SCAN testprint 401s (process:1980): libfprint-device-DEBUG: 05:08:41.701: Device reported finger status change: FP_FINGER_STATUS_NEEDED 401s (process:1980): libfprint-device-DEBUG: 05:08:41.701: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 401s (process:1980): libfprint-device-DEBUG: 05:08:41.701: Device reported finger status change: FP_FINGER_STATUS_NEEDED 401s (process:1980): libfprint-device-DEBUG: 05:08:41.701: Device reported enroll progress, reported 1 of 5 have been completed 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.702: Sleeping completed 401s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:41.702: Got a new connection! 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.702: Got instructions of length 14 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.702: Received command SCAN testprint 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.702: Processing command SCAN testprint 401s (process:1980): libfprint-device-DEBUG: 05:08:41.702: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 401s (process:1980): libfprint-device-DEBUG: 05:08:41.702: Device reported finger status change: FP_FINGER_STATUS_NEEDED 401s (process:1980): libfprint-device-DEBUG: 05:08:41.702: Device reported enroll progress, reported 2 of 5 have been completed 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.702: Sleeping completed 401s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:41.702: Got a new connection! 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.702: Got instructions of length 14 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.702: Received command SCAN testprint 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.702: Processing command SCAN testprint 401s (process:1980): libfprint-device-DEBUG: 05:08:41.702: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 401s (process:1980): libfprint-device-DEBUG: 05:08:41.702: Device reported finger status change: FP_FINGER_STATUS_NEEDED 401s (process:1980): libfprint-device-DEBUG: 05:08:41.702: Device reported enroll progress, reported 3 of 5 have been completed 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.702: Sleeping completed 401s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:41.703: Got a new connection! 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.703: Got instructions of length 14 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.703: Received command SCAN testprint 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.703: Processing command SCAN testprint 401s (process:1980): libfprint-device-DEBUG: 05:08:41.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 401s (process:1980): libfprint-device-DEBUG: 05:08:41.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED 401s (process:1980): libfprint-device-DEBUG: 05:08:41.703: Device reported enroll progress, reported 4 of 5 have been completed 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.703: Sleeping completed 401s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:41.703: Got a new connection! 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.703: Got instructions of length 14 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.703: Received command SCAN testprint 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.703: Processing command SCAN testprint 401s (process:1980): libfprint-device-DEBUG: 05:08:41.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 401s (process:1980): libfprint-device-DEBUG: 05:08:41.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED 401s (process:1980): libfprint-device-DEBUG: 05:08:41.703: Device reported enroll progress, reported 5 of 5 have been completed 401s (process:1980): libfprint-device-DEBUG: 05:08:41.703: Device reported enroll completion 401s (process:1980): libfprint-device-DEBUG: 05:08:41.703: Device reported finger status change: FP_FINGER_STATUS_NONE 401s (process:1980): libfprint-device-DEBUG: 05:08:41.703: Print for finger FP_FINGER_RIGHT_THUMB enrolled 401s (process:1980): libfprint-device-DEBUG: 05:08:41.703: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 401s (process:1980): libfprint-device-DEBUG: 05:08:41.703: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 401s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:41.703: Got a new connection! 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.704: Got instructions of length 16 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.704: Received command REMOVE testprint 401s (process:1980): libfprint-virtual_device-DEBUG: 05:08:41.704: Processing command REMOVE testprint 402s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:42.204: Deleting print testprint for user testuser 402s (process:1980): libfprint-device-DEBUG: 05:08:42.204: Device reported deletion completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.204: Completing action FPI_DEVICE_ACTION_DELETE in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.204: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.205: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.205: Got instructions of length 5 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.205: Received command CONT 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.205: Processing command CONT 402s (process:1980): libfprint-device-DEBUG: 05:08:42.205: Device reported deletion completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.205: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.205: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.205: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.205: Got instructions of length 16 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.205: Received command SET_KEEP_ALIVE 0 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.205: Keep alive toggled: 0 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.206: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.206: Got instructions of length 19 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.206: Received command SET_ENROLL_STAGES 5 402s (process:1980): libfprint-device-DEBUG: 05:08:42.206: Device reported close completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.206: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.206: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s Enroll done 402s ok 402s test_list_empty (__main__.VirtualDeviceStorage.test_list_empty) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.206: 130981200191: ../libfprint/drivers/virtual-device.c:387 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.206: 130981200213: ../libfprint/drivers/virtual-device-listener.c:153 402s (process:1980): libfprint-device-DEBUG: 05:08:42.206: Device reported open completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.206: Completing action FPI_DEVICE_ACTION_OPEN in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.206: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s (process:1980): libfprint-device-DEBUG: 05:08:42.707: Device reported listing completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.707: Completing action FPI_DEVICE_ACTION_LIST in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.707: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.707: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.707: Got instructions of length 5 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.708: Received command CONT 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.708: Processing command CONT 402s (process:1980): libfprint-device-DEBUG: 05:08:42.708: Device reported deletion completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.708: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.708: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.708: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.708: Got instructions of length 16 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.708: Received command SET_KEEP_ALIVE 0 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.708: Keep alive toggled: 0 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.708: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.708: Got instructions of length 19 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.708: Received command SET_ENROLL_STAGES 5 402s (process:1980): libfprint-device-DEBUG: 05:08:42.708: Device reported close completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.708: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.708: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s ok 402s test_list_error (__main__.VirtualDeviceStorage.test_list_error) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.709: 130981702749: ../libfprint/drivers/virtual-device.c:387 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.709: 130981702783: ../libfprint/drivers/virtual-device-listener.c:153 402s (process:1980): libfprint-device-DEBUG: 05:08:42.709: Device reported open completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.709: Completing action FPI_DEVICE_ACTION_OPEN in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.709: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.709: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.709: Got instructions of length 9 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.709: Received command SLEEP 100 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.709: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.709: Got instructions of length 7 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.709: Received command ERROR 4 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.710: Processing command SLEEP 100 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.710: Sleeping 100ms 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.810: Sleeping completed 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.810: Processing command ERROR 4 402s (process:1980): libfprint-device-DEBUG: 05:08:42.810: Device reported listing completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.810: Completing action FPI_DEVICE_ACTION_LIST in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.810: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.810: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.811: Got instructions of length 5 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.811: Received command CONT 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.811: Processing command CONT 402s (process:1980): libfprint-device-DEBUG: 05:08:42.811: Device reported deletion completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.811: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.811: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.811: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.811: Got instructions of length 16 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.811: Received command SET_KEEP_ALIVE 0 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.811: Keep alive toggled: 0 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.811: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.811: Got instructions of length 19 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.811: Received command SET_ENROLL_STAGES 5 402s (process:1980): libfprint-device-DEBUG: 05:08:42.811: Device reported close completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.811: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.811: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s ok 402s test_list_populated (__main__.VirtualDeviceStorage.test_list_populated) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.812: 130981805738: ../libfprint/drivers/virtual-device.c:387 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.812: 130981805763: ../libfprint/drivers/virtual-device-listener.c:153 402s (process:1980): libfprint-device-DEBUG: 05:08:42.812: Device reported open completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.812: Completing action FPI_DEVICE_ACTION_OPEN in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.812: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.812: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.812: Got instructions of length 9 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.812: Received command INSERT p1 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.812: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.812: Got instructions of length 7 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.812: Received command SCAN p2 402s (process:1980): libfprint-device-DEBUG: 05:08:42.813: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.813: Processing command INSERT p1 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.813: Processing command SCAN p2 402s (process:1980): libfprint-device-DEBUG: 05:08:42.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 402s (process:1980): libfprint-device-DEBUG: 05:08:42.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 402s (process:1980): libfprint-device-DEBUG: 05:08:42.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 402s (process:1980): libfprint-device-DEBUG: 05:08:42.813: Device reported enroll progress, reported 1 of 5 have been completed 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.813: Sleeping completed 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.813: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.813: Got instructions of length 7 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.813: Received command SCAN p2 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.813: Processing command SCAN p2 402s (process:1980): libfprint-device-DEBUG: 05:08:42.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 402s (process:1980): libfprint-device-DEBUG: 05:08:42.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 402s (process:1980): libfprint-device-DEBUG: 05:08:42.813: Device reported enroll progress, reported 2 of 5 have been completed 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.813: Sleeping completed 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.813: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.813: Got instructions of length 7 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.813: Received command SCAN p2 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.813: Processing command SCAN p2 402s (process:1980): libfprint-device-DEBUG: 05:08:42.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 402s (process:1980): libfprint-device-DEBUG: 05:08:42.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 402s (process:1980): libfprint-device-DEBUG: 05:08:42.813: Device reported enroll progress, reported 3 of 5 have been completed 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.814: Sleeping completed 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.814: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.814: Got instructions of length 7 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.814: Received command SCAN p2 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.814: Processing command SCAN p2 402s (process:1980): libfprint-device-DEBUG: 05:08:42.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 402s (process:1980): libfprint-device-DEBUG: 05:08:42.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED 402s (process:1980): libfprint-device-DEBUG: 05:08:42.814: Device reported enroll progress, reported 4 of 5 have been completed 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.814: Sleeping completed 402s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:42.814: Got a new connection! 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.814: Got instructions of length 7 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.814: Received command SCAN p2 402s (process:1980): libfprint-virtual_device-DEBUG: 05:08:42.814: Processing command SCAN p2 402s (process:1980): libfprint-device-DEBUG: 05:08:42.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 402s (process:1980): libfprint-device-DEBUG: 05:08:42.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED 402s (process:1980): libfprint-device-DEBUG: 05:08:42.814: Device reported enroll progress, reported 5 of 5 have been completed 402s (process:1980): libfprint-device-DEBUG: 05:08:42.814: Device reported enroll completion 402s (process:1980): libfprint-device-DEBUG: 05:08:42.814: Device reported finger status change: FP_FINGER_STATUS_NONE 402s (process:1980): libfprint-device-DEBUG: 05:08:42.814: Print for finger FP_FINGER_LEFT_LITTLE enrolled 402s (process:1980): libfprint-device-DEBUG: 05:08:42.814: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 402s (process:1980): libfprint-device-DEBUG: 05:08:42.814: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 402s Executing: libfprint-2/virtual-device.test 403s (process:1980): libfprint-device-DEBUG: 05:08:43.315: Device reported listing completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.315: Completing action FPI_DEVICE_ACTION_LIST in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.315: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.317: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.317: Got instructions of length 5 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.317: Received command CONT 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.317: Processing command CONT 403s (process:1980): libfprint-device-DEBUG: 05:08:43.317: Device reported deletion completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.317: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.317: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.317: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.318: Got instructions of length 16 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.318: Received command SET_KEEP_ALIVE 0 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.318: Keep alive toggled: 0 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.318: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.318: Got instructions of length 19 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.318: Received command SET_ENROLL_STAGES 5 403s (process:1980): libfprint-device-DEBUG: 05:08:43.319: Device reported close completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.319: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.319: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s Enroll done 403s ok 403s test_open_error (__main__.VirtualDeviceStorage.test_open_error) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.319: 130982313376: ../libfprint/drivers/virtual-device.c:387 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.319: 130982313426: ../libfprint/drivers/virtual-device-listener.c:153 403s (process:1980): libfprint-device-DEBUG: 05:08:43.319: Device reported open completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.320: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.320: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.320: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.320: Got instructions of length 16 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.320: Received command IGNORED_COMMAND 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.320: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.320: Got instructions of length 7 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.320: Received command ERROR 5 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.321: Processing command IGNORED_COMMAND 403s (process:1980): libfprint-device-DEBUG: 05:08:43.321: Device reported close completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.321: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.321: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.321: 130982315451: ../libfprint/drivers/virtual-device.c:387 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.321: Processing command ERROR 5 403s (process:1980): libfprint-device-DEBUG: 05:08:43.321: Device reported open completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.321: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.321: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s ok 403s test_open_error_with_keep_alive (__main__.VirtualDeviceStorage.test_open_error_with_keep_alive) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.322: 130982315799: ../libfprint/drivers/virtual-device.c:387 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.322: 130982315818: ../libfprint/drivers/virtual-device-listener.c:153 403s (process:1980): libfprint-device-DEBUG: 05:08:43.322: Device reported open completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.322: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.322: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.322: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.322: Got instructions of length 16 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.322: Received command SET_KEEP_ALIVE 1 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.322: Keep alive toggled: 1 403s (process:1980): libfprint-device-DEBUG: 05:08:43.322: Device reported close completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.322: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.322: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.323: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.323: Got instructions of length 7 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.323: Received command ERROR 5 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.323: 130982317050: ../libfprint/drivers/virtual-device.c:387 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.323: Processing command ERROR 5 403s (process:1980): libfprint-device-DEBUG: 05:08:43.323: Device reported open completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.323: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s ok 403s test_quick_enroll (__main__.VirtualDeviceStorage.test_quick_enroll) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.323: 130982317344: ../libfprint/drivers/virtual-device.c:387 403s (process:1980): libfprint-device-DEBUG: 05:08:43.323: Device reported open completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.323: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.323: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.323: Got instructions of length 19 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.323: Received command SET_ENROLL_STAGES 1 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.324: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.324: Got instructions of length 14 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.324: Received command SCAN testprint 403s (process:1980): libfprint-device-DEBUG: 05:08:43.324: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.324: Processing command SCAN testprint 403s (process:1980): libfprint-device-DEBUG: 05:08:43.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 403s (process:1980): libfprint-device-DEBUG: 05:08:43.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 403s (process:1980): libfprint-device-DEBUG: 05:08:43.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 403s (process:1980): libfprint-device-DEBUG: 05:08:43.324: Device reported enroll progress, reported 1 of 1 have been completed 403s (process:1980): libfprint-device-DEBUG: 05:08:43.324: Device reported enroll completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.324: Device reported finger status change: FP_FINGER_STATUS_NONE 403s (process:1980): libfprint-device-DEBUG: 05:08:43.324: Print for finger FP_FINGER_LEFT_LITTLE enrolled 403s (process:1980): libfprint-device-DEBUG: 05:08:43.324: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.324: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.324: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.325: Got instructions of length 5 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.325: Received command CONT 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.325: Processing command CONT 403s (process:1980): libfprint-device-DEBUG: 05:08:43.325: Device reported deletion completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.325: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.325: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.325: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.325: Got instructions of length 16 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.325: Received command SET_KEEP_ALIVE 0 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.325: Keep alive toggled: 0 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.325: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.325: Got instructions of length 19 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.325: Received command SET_ENROLL_STAGES 5 403s (process:1980): libfprint-device-DEBUG: 05:08:43.325: Device reported close completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.325: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.325: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s Enroll done 403s ok 403s test_verify_missing_print (__main__.VirtualDeviceStorage.test_verify_missing_print) ... (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.325: 130982319495: ../libfprint/drivers/virtual-device.c:387 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.325: 130982319510: ../libfprint/drivers/virtual-device-listener.c:153 403s (process:1980): libfprint-device-DEBUG: 05:08:43.325: Device reported open completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.325: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.325: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.326: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.326: Got instructions of length 23 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.326: Received command SCAN not-existing-print 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.326: Processing command SCAN not-existing-print 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Device reported finger status change: FP_FINGER_STATUS_NEEDED 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.326: Virtual device scanned print not-existing-print 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Device reported verify result 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Device reported finger status change: FP_FINGER_STATUS_NEEDED 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Device reported verify completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Device reported finger status change: FP_FINGER_STATUS_NONE 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.326: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.326: Got instructions of length 5 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.326: Received command CONT 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.326: Processing command CONT 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Device reported deletion completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.326: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.327: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.327: Got instructions of length 16 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.327: Received command SET_KEEP_ALIVE 0 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.327: Keep alive toggled: 0 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.327: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.327: Got instructions of length 19 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.327: Received command SET_ENROLL_STAGES 5 403s (process:1980): libfprint-device-DEBUG: 05:08:43.327: Device reported close completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.327: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.327: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s ok 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.327: 130982321498: ../libfprint/drivers/virtual-device.c:752 403s test_device_unplug (__main__.VirtualDeviceUnplugging.test_device_unplug) ... (process:1980): libfprint-context-DEBUG: 05:08:43.328: Initializing FpContext (libfprint version 1.94.9+tod1) 403s (process:1980): libfprint-tod-DEBUG: 05:08:43.328: 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 (process:1980): libfprint-context-DEBUG: 05:08:43.331: No driver found for USB device 1D6B:0003 403s (process:1980): libfprint-context-DEBUG: 05:08:43.331: No driver found for USB device 0627:0001 403s (process:1980): libfprint-context-DEBUG: 05:08:43.331: No driver found for USB device 1D6B:0002 403s (process:1980): libfprint-context-DEBUG: 05:08:43.331: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-pxcv1dcj/virtual-device.socket 403s (process:1980): libfprint-context-DEBUG: 05:08:43.331: created 403s (process:1980): libfprint-context-DEBUG: 05:08:43.331: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-6yt098ul/virtual-device-storage.socket 403s (process:1980): libfprint-context-DEBUG: 05:08:43.331: created 403s (process:1980): libfprint-device-DEBUG: 05:08:43.332: Device reported probe completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.332: Device reported probe completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.332: Completing action FPI_DEVICE_ACTION_PROBE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.332: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (process:1980): libfprint-device-DEBUG: 05:08:43.332: Completing action FPI_DEVICE_ACTION_PROBE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.332: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.332: 130982325885: ../libfprint/drivers/virtual-device.c:387 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.332: 130982325903: ../libfprint/drivers/virtual-device-listener.c:153 403s (process:1980): libfprint-device-DEBUG: 05:08:43.332: Device reported open completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.332: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.332: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.332: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.332: Got instructions of length 7 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.332: Received command UNPLUG 403s (process:1980): libfprint-device-DEBUG: 05:08:43.333: Device reported close completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.333: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.333: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.333: 130982326985: ../libfprint/drivers/virtual-device.c:752 403s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:43.333: 130982327041: ../libfprint/drivers/virtual-device-storage.c:253 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.333: 130982327059: ../libfprint/drivers/virtual-device.c:752 403s ok 403s test_device_unplug_during_verify (__main__.VirtualDeviceUnplugging.test_device_unplug_during_verify) ... (process:1980): libfprint-context-DEBUG: 05:08:43.333: Initializing FpContext (libfprint version 1.94.9+tod1) 403s (process:1980): libfprint-tod-DEBUG: 05:08:43.333: 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 (process:1980): libfprint-context-DEBUG: 05:08:43.335: No driver found for USB device 1D6B:0003 403s (process:1980): libfprint-context-DEBUG: 05:08:43.335: No driver found for USB device 0627:0001 403s (process:1980): libfprint-context-DEBUG: 05:08:43.335: No driver found for USB device 1D6B:0002 403s (process:1980): libfprint-context-DEBUG: 05:08:43.335: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-pxcv1dcj/virtual-device.socket 403s (process:1980): libfprint-context-DEBUG: 05:08:43.335: created 403s (process:1980): libfprint-context-DEBUG: 05:08:43.335: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-6yt098ul/virtual-device-storage.socket 403s (process:1980): libfprint-context-DEBUG: 05:08:43.335: created 403s (process:1980): libfprint-device-DEBUG: 05:08:43.336: Device reported probe completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.336: Device reported probe completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.336: Completing action FPI_DEVICE_ACTION_PROBE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.336: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (process:1980): libfprint-device-DEBUG: 05:08:43.336: Completing action FPI_DEVICE_ACTION_PROBE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.336: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.336: 130982330493: ../libfprint/drivers/virtual-device.c:387 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.336: 130982330514: ../libfprint/drivers/virtual-device-listener.c:153 403s (process:1980): libfprint-device-DEBUG: 05:08:43.336: Device reported open completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.336: Completing action FPI_DEVICE_ACTION_OPEN in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.336: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (process:1980): libfprint-device-DEBUG: 05:08:43.337: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 403s (process:1980): libfprint-device-DEBUG: 05:08:43.337: Device reported finger status change: FP_FINGER_STATUS_NEEDED 403s (process:1980): libfprint-virtual_device_connection-DEBUG: 05:08:43.337: Got a new connection! 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.337: Got instructions of length 7 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.337: Received command UNPLUG 403s (process:1980): libfprint-device-DEBUG: 05:08:43.437: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-device-DEBUG: 05:08:43.838: Device reported generic error (No commands arrived in time to run!) during action; action was: FPI_DEVICE_ACTION_VERIFY 403s (process:1980): libfprint-device-DEBUG: 05:08:43.838: Device reported verify completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.838: Device reported finger status change: FP_FINGER_STATUS_NONE 403s (process:1980): libfprint-device-DEBUG: 05:08:43.838: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.838: Updated temperature model after 0.40 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-device-DEBUG: 05:08:43.838: Device reported close completion 403s (process:1980): libfprint-device-DEBUG: 05:08:43.838: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 403s (process:1980): libfprint-device-DEBUG: 05:08:43.838: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.838: 130982832536: ../libfprint/drivers/virtual-device.c:752 403s (process:1980): libfprint-virtual_device_storage-DEBUG: 05:08:43.838: 130982832602: ../libfprint/drivers/virtual-device-storage.c:253 403s (process:1980): libfprint-virtual_device-DEBUG: 05:08:43.838: 130982832609: ../libfprint/drivers/virtual-device.c:752 403s ok 403s 403s ---------------------------------------------------------------------- 403s Ran 86 tests in 17.632s 403s 403s OK (skipped=1) 403s PASS: libfprint-2/virtual-device.test 403s Running test: libfprint-2/driver-focaltech_moc.test 403s ** (umockdev-run:1998): DEBUG: 05:08:43.921: umockdev.vala:127: Created udev test bed /tmp/umockdev.TXZ912 403s ** (umockdev-run:1998): DEBUG: 05:08:43.921: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 403s ** (umockdev-run:1998): DEBUG: 05:08:43.927: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 (subsystem usb) 403s ** (umockdev-run:1998): DEBUG: 05:08:43.932: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TXZ912/dev/bus/usb/003/006 403s ** (umockdev-run:1998): DEBUG: 05:08:43.932: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 403s ** (umockdev-run:1998): DEBUG: 05:08:43.938: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 (subsystem usb) 403s ** (umockdev-run:1998): DEBUG: 05:08:43.941: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TXZ912/dev/bus/usb/003/002 403s ** (umockdev-run:1998): DEBUG: 05:08:43.942: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 403s ** (umockdev-run:1998): DEBUG: 05:08:43.947: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 (subsystem usb) 403s ** (umockdev-run:1998): DEBUG: 05:08:43.951: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TXZ912/dev/bus/usb/003/001 403s ** (umockdev-run:1998): DEBUG: 05:08:43.951: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 403s ** (umockdev-run:1998): DEBUG: 05:08:43.954: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 (subsystem pci) 403s ** (umockdev-run:1998): DEBUG: 05:08:43.959: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4 403s ** (umockdev-run:1998): DEBUG: 05:08:43.959: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4 (subsystem pci) 404s (process:2002): libfprint-context-DEBUG: 05:08:44.065: Initializing FpContext (libfprint version 1.94.9+tod1) 404s (process:2002): libfprint-tod-DEBUG: 05:08:44.065: 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:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.068: 130983062458: ../libfprint/drivers/focaltech_moc/focaltech_moc.c:1852 404s (process:2002): libfprint-context-DEBUG: 05:08:44.069: No driver found for USB device 05E3:0608 404s (process:2002): libfprint-context-DEBUG: 05:08:44.069: No driver found for USB device 1D6B:0002 404s (process:2002): libfprint-device-DEBUG: 05:08:44.069: Device reported probe completion 404s (process:2002): libfprint-device-DEBUG: 05:08:44.069: Completing action FPI_DEVICE_ACTION_PROBE in idle! 404s (process:2002): libfprint-device-DEBUG: 05:08:44.069: Not updating temperature model, device can run continuously! 404s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.071: class:dc, subclass:a0, protocol:b0 404s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.071: bytes size:0 404s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.071: 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 404s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.071: bytes size:0 404s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.071: 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 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.071: [focaltech_moc] DEV_INIT_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.071: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 404s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.072: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.073: focaltechmoc enroll_times: 10 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.073: [focaltech_moc] DEV_INIT_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.073: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.073: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.073: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.074: [focaltech_moc] DEV_INIT_STATES completed successfully 404s (process:2002): libfprint-device-DEBUG: 05:08:44.074: Device reported open completion 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.074: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-device-DEBUG: 05:08:44.074: Completing action FPI_DEVICE_ACTION_OPEN in idle! 404s (process:2002): libfprint-device-DEBUG: 05:08:44.074: Not updating temperature model, device can run continuously! 404s (process:2002): libfprint-device-DEBUG: 05:08:44.075: Not updating temperature model, device can run continuously! 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.075: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.075: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.075: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.076: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.076: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.076: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.076: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.077: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 2 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.077: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.077: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.077: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.078: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 3 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.078: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.078: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.078: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.079: focaltechmoc user id: FP1-00000000-0-00000000-nobody 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.079: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.079: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.079: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.079: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.080: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.080: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.130: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.130: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.131: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.131: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.131: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.181: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.181: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.182: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.183: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.183: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.233: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.233: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.234: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.235: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.235: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.285: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.285: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.286: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.286: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.286: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.337: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.337: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.337: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.338: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.338: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.388: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.388: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.389: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.389: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.389: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.389: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.390: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-device-DEBUG: 05:08:44.390: Device reported enroll progress, reported 1 of 10 have been completed 404s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.390: focaltechmoc remain: 9 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.390: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.390: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.391: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.391: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.391: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.391: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.442: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.442: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.442: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.443: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.443: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.493: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.493: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.494: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.494: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.494: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.544: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.545: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.545: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.546: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.546: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.596: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.596: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.597: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.597: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.597: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.647: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.647: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.648: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.648: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.649: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.649: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.649: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-device-DEBUG: 05:08:44.650: Device reported enroll progress, reported 2 of 10 have been completed 404s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.650: focaltechmoc remain: 8 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.650: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.650: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.650: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.650: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.651: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.651: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.701: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.701: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.702: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.702: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.702: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.703: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.703: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-device-DEBUG: 05:08:44.703: Device reported enroll progress, reported 3 of 10 have been completed 404s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.703: focaltechmoc remain: 7 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.703: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.703: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.704: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.704: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.704: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.704: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.755: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.755: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.755: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.756: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.756: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.806: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.806: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.807: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.807: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.807: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.857: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.857: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.858: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.859: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.859: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.909: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.909: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.910: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.910: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.910: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.960: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.960: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.961: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.962: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.962: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.962: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.962: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-device-DEBUG: 05:08:44.963: Device reported enroll progress, reported 4 of 10 have been completed 404s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:44.963: focaltechmoc remain: 6 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.963: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.963: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.964: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.964: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.964: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 404s (process:2002): libfprint-SSM-DEBUG: 05:08:44.964: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.015: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.015: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.015: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.016: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.016: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.066: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.066: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.067: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.067: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.067: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.117: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.117: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.118: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.119: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.119: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.119: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.119: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-device-DEBUG: 05:08:45.120: Device reported enroll progress, reported 5 of 10 have been completed 405s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:45.120: focaltechmoc remain: 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.120: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.120: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.120: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.120: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.121: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.121: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.171: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.171: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.171: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.172: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.172: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.222: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.222: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.223: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.224: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.224: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.274: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.274: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.275: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.275: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.275: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.325: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.325: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.326: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.327: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.327: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.327: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.327: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-device-DEBUG: 05:08:45.328: Device reported enroll progress, reported 6 of 10 have been completed 405s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:45.328: focaltechmoc remain: 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.328: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.328: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.328: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.328: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.329: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.329: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.329: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.329: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-device-DEBUG: 05:08:45.330: Device reported enroll progress, reported 6 of 10 have been completed 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.330: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.330: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.330: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.330: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.331: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.331: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.381: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.381: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.382: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.382: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.382: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.433: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.433: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.434: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.434: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.434: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.484: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.485: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.485: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.486: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.486: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.536: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.536: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.537: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.537: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.537: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.538: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.538: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-device-DEBUG: 05:08:45.539: Device reported enroll progress, reported 7 of 10 have been completed 405s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:45.539: focaltechmoc remain: 3 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.539: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.539: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.539: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.539: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.540: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.540: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.590: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.590: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.591: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.591: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.591: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.642: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.642: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.642: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.643: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.643: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.643: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.643: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-device-DEBUG: 05:08:45.644: Device reported enroll progress, reported 8 of 10 have been completed 405s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:45.644: focaltechmoc remain: 2 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.644: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.644: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.644: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.645: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.645: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.645: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.695: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.695: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.696: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.697: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.697: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.697: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.697: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-device-DEBUG: 05:08:45.698: Device reported enroll progress, reported 9 of 10 have been completed 405s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:45.698: focaltechmoc remain: 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.698: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.698: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.698: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.698: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.699: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.699: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.749: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.749: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.750: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.750: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.751: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.751: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.751: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-device-DEBUG: 05:08:45.752: Device reported enroll progress, reported 10 of 10 have been completed 405s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:45.752: focaltechmoc remain: 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.752: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 7 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.752: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.752: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.752: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.753: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 8 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.753: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.753: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.753: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:45.754: focaltech_moc_commit_cb success 405s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:45.754: Enrollment was successful! 405s (process:2002): libfprint-device-DEBUG: 05:08:45.754: Device reported enroll completion 405s (process:2002): libfprint-device-DEBUG: 05:08:45.754: Print for finger FP_FINGER_UNKNOWN enrolled 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.754: [focaltech_moc] MOC_ENROLL_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.754: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-device-DEBUG: 05:08:45.754: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 405s (process:2002): libfprint-device-DEBUG: 05:08:45.754: Not updating temperature model, device can run continuously! 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.754: [focaltech_moc] MOC_LIST_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.754: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.755: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.755: [focaltech_moc] MOC_LIST_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.755: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.756: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.756: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:45.757: focaltechmoc add slot: 0 405s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:45.757: FP1-00000000-0-00000000-nobody 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.757: [focaltech_moc] MOC_LIST_NUM_STATES entering state 2 405s (process:2002): libfprint-device-DEBUG: 05:08:45.757: Device reported listing completion 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.757: [focaltech_moc] MOC_LIST_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.757: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-device-DEBUG: 05:08:45.757: Completing action FPI_DEVICE_ACTION_LIST in idle! 405s (process:2002): libfprint-device-DEBUG: 05:08:45.757: Not updating temperature model, device can run continuously! 405s (process:2002): libfprint-device-DEBUG: 05:08:45.757: Not updating temperature model, device can run continuously! 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.757: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.757: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.758: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.758: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.758: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.758: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.759: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.759: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.759: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.809: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.810: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.810: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.811: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.811: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.861: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.861: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.862: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.862: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.862: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.913: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.913: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.913: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.914: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.914: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.964: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.964: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.965: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.966: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.966: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.966: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.966: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.967: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.967: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.967: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.967: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-device-DEBUG: 05:08:45.968: Device reported verify result 405s (process:2002): libfprint-device-DEBUG: 05:08:45.968: Device reported verify completion 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.968: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.968: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-device-DEBUG: 05:08:45.968: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 405s (process:2002): libfprint-device-DEBUG: 05:08:45.968: Not updating temperature model, device can run continuously! 405s (process:2002): libfprint-device-DEBUG: 05:08:45.968: Not updating temperature model, device can run continuously! 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.968: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.968: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.969: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.970: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.970: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.970: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.970: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.971: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 405s (process:2002): libfprint-SSM-DEBUG: 05:08:45.971: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.021: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.021: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.022: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.022: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.022: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.072: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.072: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.073: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.074: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.074: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.074: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.074: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.075: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.075: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.075: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.076: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 406s (process:2002): libfprint-device-DEBUG: 05:08:46.076: Device reported identify result 406s (process:2002): libfprint-device-DEBUG: 05:08:46.076: Device reported identify completion 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.076: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.076: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 406s (process:2002): libfprint-device-DEBUG: 05:08:46.076: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 406s (process:2002): libfprint-device-DEBUG: 05:08:46.076: Not updating temperature model, device can run continuously! 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.077: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 0 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.077: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.077: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.078: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 1 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.078: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.078: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.078: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 406s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:46.079: focaltechmoc add slot: 0 406s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:46.079: FP1-00000000-0-00000000-nobody 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.079: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 2 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.079: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.079: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.080: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.080: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.080: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.080: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.081: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 406s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:46.081: delete slot 0 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.081: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.081: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 4 406s (process:2002): libfprint-device-DEBUG: 05:08:46.081: Device reported deletion completion 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.081: [focaltech_moc] MOC_DELETE_NUM_STATES completed successfully 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.081: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 406s (process:2002): libfprint-device-DEBUG: 05:08:46.081: Completing action FPI_DEVICE_ACTION_DELETE in idle! 406s (process:2002): libfprint-device-DEBUG: 05:08:46.081: Not updating temperature model, device can run continuously! 406s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:46.081: Focaltechmoc dev_exit 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.081: [focaltech_moc] DEV_EXIT_STATES entering state 0 406s (process:2002): libfprint-SSM-DEBUG: 05:08:46.081: [focaltech_moc] DEV_EXIT_STATES completed successfully 406s (process:2002): libfprint-focaltech_moc-DEBUG: 05:08:46.081: class:dc, subclass:a0, protocol:b0 406s (process:2002): libfprint-device-DEBUG: 05:08:46.082: Device reported close completion 406s (process:2002): libfprint-device-DEBUG: 05:08:46.082: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 406s (process:2002): libfprint-device-DEBUG: 05:08:46.082: Not updating temperature model, device can run continuously! 406s enrolling 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf10ff4a8 (FpiDeviceFocaltechMoc at 0x1cf7ba8)>, 1, None, None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf10ff4a8 (FpiDeviceFocaltechMoc at 0x1cf7ba8)>, 2, None, None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf10ff4a8 (FpiDeviceFocaltechMoc at 0x1cf7ba8)>, 3, None, None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf10ff4a8 (FpiDeviceFocaltechMoc at 0x1cf7ba8)>, 4, None, None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf10ff4a8 (FpiDeviceFocaltechMoc at 0x1cf7ba8)>, 5, None, None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf10ff4a8 (FpiDeviceFocaltechMoc at 0x1cf7ba8)>, 6, None, None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf10ff4a8 (FpiDeviceFocaltechMoc at 0x1cf7ba8)>, 6, 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__.FpiDeviceFocaltechMoc object at 0xf10ff4a8 (FpiDeviceFocaltechMoc at 0x1cf7ba8)>, 7, None, None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf10ff4a8 (FpiDeviceFocaltechMoc at 0x1cf7ba8)>, 8, None, None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf10ff4a8 (FpiDeviceFocaltechMoc at 0x1cf7ba8)>, 9, None, None, None) 406s finger status: 406s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf10ff4a8 (FpiDeviceFocaltechMoc at 0x1cf7ba8)>, 10, None, None, None) 406s enroll done 406s listing 406s listing done 406s verifying 406s verify done 406s async identifying 406s indentification_done: 406s deleting 406s delete done 406s ** (umockdev-run:1998): DEBUG: 05:08:46.107: umockdev.vala:154: Removing test bed /tmp/umockdev.TXZ912 406s (umockdev-run:1998): GLib-DEBUG: 05:08:46.118: unsetenv() is not thread-safe and should not be used after threads are created 406s PASS: libfprint-2/driver-focaltech_moc.test 406s Running test: libfprint-2/driver-vfs301.test 406s ** (umockdev-run:2010): DEBUG: 05:08:46.177: umockdev.vala:127: Created udev test bed /tmp/umockdev.63EG22 406s ** (umockdev-run:2010): DEBUG: 05:08:46.177: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 406s ** (umockdev-run:2010): DEBUG: 05:08:46.179: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 (subsystem usb) 406s ** (umockdev-run:2010): DEBUG: 05:08:46.183: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.63EG22/dev/bus/usb/002/005 406s ** (umockdev-run:2010): DEBUG: 05:08:46.183: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1 406s ** (umockdev-run:2010): DEBUG: 05:08:46.184: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1 (subsystem usb) 406s ** (umockdev-run:2010): DEBUG: 05:08:46.188: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.63EG22/dev/bus/usb/002/002 406s ** (umockdev-run:2010): DEBUG: 05:08:46.188: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2 406s ** (umockdev-run:2010): DEBUG: 05:08:46.189: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2 (subsystem usb) 406s ** (umockdev-run:2010): DEBUG: 05:08:46.193: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.63EG22/dev/bus/usb/002/001 406s ** (umockdev-run:2010): DEBUG: 05:08:46.193: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0 406s ** (umockdev-run:2010): DEBUG: 05:08:46.193: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0 (subsystem pci) 406s (umockdev-run:2010): GLib-GIO-DEBUG: 05:08:46.196: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 406s (process:2014): libfprint-context-DEBUG: 05:08:46.337: Initializing FpContext (libfprint version 1.94.9+tod1) 406s (process:2014): libfprint-tod-DEBUG: 05:08:46.337: 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:2014): libfprint-context-DEBUG: 05:08:46.341: No driver found for USB device 8087:0020 406s (process:2014): libfprint-context-DEBUG: 05:08:46.341: No driver found for USB device 1D6B:0002 406s (process:2014): libfprint-device-DEBUG: 05:08:46.342: Device reported probe completion 406s (process:2014): libfprint-device-DEBUG: 05:08:46.342: Completing action FPI_DEVICE_ACTION_PROBE in idle! 406s (process:2014): libfprint-device-DEBUG: 05:08:46.342: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2014): libfprint-image_device-DEBUG: 05:08:46.344: Image device open completed 406s (process:2014): libfprint-device-DEBUG: 05:08:46.344: Device reported open completion 406s (process:2014): libfprint-device-DEBUG: 05:08:46.344: Completing action FPI_DEVICE_ACTION_OPEN in idle! 406s (process:2014): libfprint-device-DEBUG: 05:08:46.344: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2014): libfprint-device-DEBUG: 05:08:46.344: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 406s (process:2014): libfprint-image_device-DEBUG: 05:08:46.344: Activating image device 406s (process:2014): libfprint-image_device-DEBUG: 05:08:46.344: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 406s (process:2014): libfprint-SSM-DEBUG: 05:08:46.344: [vfs301] 1 entering state 0 406s (process:2014): libfprint-SSM-DEBUG: 05:08:46.384: [vfs301] 1 completed successfully 406s (process:2014): libfprint-image_device-DEBUG: 05:08:46.384: Image device activation completed 406s (process:2014): libfprint-image_device-DEBUG: 05:08:46.384: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 406s (process:2014): libfprint-image_device-DEBUG: 05:08:46.384: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 406s (process:2014): libfprint-SSM-DEBUG: 05:08:46.384: [vfs301] M_LOOP_NUM_STATES entering state 0 406s (process:2014): libfprint-SSM-DEBUG: 05:08:46.385: [vfs301] M_LOOP_NUM_STATES entering state 1 406s (process:2014): libfprint-device-DEBUG: 05:08:46.385: Device reported finger status change: FP_FINGER_STATUS_NEEDED 406s (process:2014): libfprint-device-DEBUG: 05:08:46.444: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 406s (process:2014): libfprint-SSM-DEBUG: 05:08:46.586: [vfs301] M_LOOP_NUM_STATES entering state 2 406s (process:2014): libfprint-SSM-DEBUG: 05:08:46.587: [vfs301] M_LOOP_NUM_STATES entering state 1 406s (process:2014): libfprint-SSM-DEBUG: 05:08:46.787: [vfs301] M_LOOP_NUM_STATES entering state 2 406s (process:2014): libfprint-SSM-DEBUG: 05:08:46.788: [vfs301] M_LOOP_NUM_STATES entering state 3 406s (process:2014): libfprint-device-DEBUG: 05:08:46.788: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 406s (process:2014): libfprint-image_device-DEBUG: 05:08:46.788: Image device reported finger status: on 406s (process:2014): libfprint-image_device-DEBUG: 05:08:46.788: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 406s (process:2014): libfprint-SSM-DEBUG: 05:08:46.789: [vfs301] M_LOOP_NUM_STATES entering state 4 407s (process:2014): libfprint-SSM-DEBUG: 05:08:46.989: [vfs301] M_LOOP_NUM_STATES entering state 5 407s (process:2014): libfprint-SSM-DEBUG: 05:08:46.994: [vfs301] M_LOOP_NUM_STATES entering state 6 407s (process:2014): libfprint-image_device-DEBUG: 05:08:46.995: Image device captured an image 407s (process:2014): libfprint-image_device-DEBUG: 05:08:46.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 407s (process:2014): libfprint-device-DEBUG: 05:08:46.996: Device reported finger status change: FP_FINGER_STATUS_PRESENT 407s (process:2014): libfprint-SSM-DEBUG: 05:08:46.996: [vfs301] M_LOOP_NUM_STATES completed successfully 407s (process:2014): libfprint-device-DEBUG: 05:08:46.996: Device reported finger status change: FP_FINGER_STATUS_NONE 407s (process:2014): libfprint-image_device-DEBUG: 05:08:46.996: Image device reported finger status: off 407s (process:2014): libfprint-image_device-DEBUG: 05:08:46.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 407s (process:2014): libfprint-image_device-DEBUG: 05:08:46.996: Deactivating image device 407s (process:2014): libfprint-image_device-DEBUG: 05:08:46.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 407s (process:2014): libfprint-image_device-DEBUG: 05:08:46.996: Image device deactivation completed 407s (process:2014): libfprint-image_device-DEBUG: 05:08:46.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 407s (process:2014): libfprint-image-DEBUG: 05:08:47.016: Minutiae scan completed in 0.020154 secs 407s (process:2014): libfprint-device-DEBUG: 05:08:47.016: Device reported capture completion 407s (process:2014): libfprint-device-DEBUG: 05:08:47.016: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 407s (process:2014): libfprint-device-DEBUG: 05:08:47.016: Updated temperature model after 0.57 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 407s (process:2014): libfprint-image_device-DEBUG: 05:08:47.017: Image device close completed 407s (process:2014): libfprint-device-DEBUG: 05:08:47.017: Device reported close completion 407s (process:2014): libfprint-device-DEBUG: 05:08:47.017: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 407s (process:2014): libfprint-device-DEBUG: 05:08:47.017: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 407s ** (umockdev-run:2010): DEBUG: 05:08:47.112: umockdev.vala:154: Removing test bed /tmp/umockdev.63EG22 407s (umockdev-run:2010): GLib-DEBUG: 05:08:47.121: unsetenv() is not thread-safe and should not be used after threads are created 407s Comparing PNGs /tmp/libfprint-umockdev-test-hqs5vyeb/capture.png and /usr/share/installed-tests/libfprint-2/vfs301/capture.png 407s PASS: libfprint-2/driver-vfs301.test 407s Running test: libfprint-2/driver-aes2501.test 407s ** (umockdev-run:2023): DEBUG: 05:08:47.196: umockdev.vala:127: Created udev test bed /tmp/umockdev.RW1F22 407s ** (umockdev-run:2023): DEBUG: 05:08:47.196: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 407s ** (umockdev-run:2023): DEBUG: 05:08:47.198: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 407s ** (umockdev-run:2023): DEBUG: 05:08:47.202: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.RW1F22/dev/bus/usb/001/044 407s ** (umockdev-run:2023): DEBUG: 05:08:47.202: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 407s ** (umockdev-run:2023): DEBUG: 05:08:47.203: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 407s ** (umockdev-run:2023): DEBUG: 05:08:47.207: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.RW1F22/dev/bus/usb/001/001 407s ** (umockdev-run:2023): DEBUG: 05:08:47.207: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 407s ** (umockdev-run:2023): DEBUG: 05:08:47.207: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 407s (process:2027): libfprint-context-DEBUG: 05:08:47.436: Initializing FpContext (libfprint version 1.94.9+tod1) 407s (process:2027): libfprint-tod-DEBUG: 05:08:47.437: 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 (process:2027): libfprint-context-DEBUG: 05:08:47.442: No driver found for USB device 1D6B:0002 407s (process:2027): libfprint-device-DEBUG: 05:08:47.443: Device reported probe completion 407s (process:2027): libfprint-device-DEBUG: 05:08:47.443: Completing action FPI_DEVICE_ACTION_PROBE in idle! 407s (process:2027): libfprint-device-DEBUG: 05:08:47.443: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 407s (process:2027): libfprint-image_device-DEBUG: 05:08:47.447: Image device open completed 407s (process:2027): libfprint-device-DEBUG: 05:08:47.447: Device reported open completion 407s (process:2027): libfprint-device-DEBUG: 05:08:47.447: Completing action FPI_DEVICE_ACTION_OPEN in idle! 407s (process:2027): libfprint-device-DEBUG: 05:08:47.447: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 407s (process:2027): libfprint-device-DEBUG: 05:08:47.448: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 407s (process:2027): libfprint-image_device-DEBUG: 05:08:47.448: Activating image device 407s (process:2027): libfprint-image_device-DEBUG: 05:08:47.448: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 407s (process:2027): libfprint-SSM-DEBUG: 05:08:47.448: [aes2501] ACTIVATE_NUM_STATES entering state 0 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.448: write 38 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.451: all registers written 407s (process:2027): libfprint-SSM-DEBUG: 05:08:47.451: [aes2501] ACTIVATE_NUM_STATES entering state 1 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.451: read data 1 407s (process:2027): libfprint-SSM-DEBUG: 05:08:47.451: [aes2501] ACTIVATE_NUM_STATES entering state 2 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.451: write 7 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.452: all registers written 407s (process:2027): libfprint-SSM-DEBUG: 05:08:47.452: [aes2501] ACTIVATE_NUM_STATES entering state 3 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.452: 130986446292: ../libfprint/drivers/aes2501.c:140 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.452: write 1 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.453: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.453: reg 0xaf = 20 407s (process:2027): libfprint-SSM-DEBUG: 05:08:47.453: [aes2501] ACTIVATE_NUM_STATES entering state 5 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.453: write 7 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.454: all registers written 407s (process:2027): libfprint-SSM-DEBUG: 05:08:47.454: [aes2501] ACTIVATE_NUM_STATES entering state 6 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.454: write 16 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.455: all registers written 407s (process:2027): libfprint-SSM-DEBUG: 05:08:47.455: [aes2501] ACTIVATE_NUM_STATES completed successfully 407s (process:2027): libfprint-image_device-DEBUG: 05:08:47.455: Image device activation completed 407s (process:2027): libfprint-image_device-DEBUG: 05:08:47.455: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 407s (process:2027): libfprint-image_device-DEBUG: 05:08:47.455: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 407s (process:2027): libfprint-device-DEBUG: 05:08:47.455: Device reported finger status change: FP_FINGER_STATUS_NEEDED 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.455: 130986448978: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.455: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.460: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.461: 130986454859: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.461: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.463: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.464: 130986457951: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.464: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.466: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.466: 130986460705: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.467: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.468: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.469: 130986463428: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.469: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.471: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.472: 130986465979: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.472: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.474: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.474: 130986468626: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.474: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.477: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.477: 130986471436: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.477: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.479: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.480: 130986474061: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.480: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.482: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.482: 130986476638: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.482: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.484: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.485: 130986479460: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.485: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.487: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.488: 130986482101: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.488: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.490: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.491: 130986484783: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.491: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.493: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.493: 130986487636: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.493: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.495: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.496: 130986490364: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.496: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.498: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.499: 130986493065: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.499: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.501: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.502: 130986496165: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.502: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.504: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.505: 130986499077: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.505: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.507: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.508: 130986502172: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.508: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.510: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.510: 130986504655: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.510: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.512: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.513: 130986507062: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.513: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.515: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.515: 130986509444: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.515: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.517: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.518: 130986511857: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.518: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.519: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.520: 130986514252: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.520: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.522: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.522: 130986516500: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.522: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.524: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.524: 130986518509: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.524: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.526: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.526: 130986520691: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.526: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.528: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.528: 130986522718: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.529: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.530: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.531: 130986525092: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.531: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.532: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.533: 130986527215: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.533: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.535: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.535: 130986529249: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.535: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.537: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.537: 130986531534: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.537: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.539: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.540: 130986533935: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.540: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.541: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.542: 130986535984: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.542: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.543: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.544: 130986538027: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.544: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.546: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.547: 130986540968: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.547: write 23 regs 407s (process:2027): libfprint-device-DEBUG: 05:08:47.547: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.548: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.549: 130986542988: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.549: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.550: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.551: 130986545034: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.551: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.553: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.553: 130986547637: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.553: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.555: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.555: 130986549669: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.555: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.557: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.557: 130986551699: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.557: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.559: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.560: 130986553784: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.560: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.561: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.562: 130986555817: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.562: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.563: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.564: 130986557876: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.564: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.565: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.566: 130986560094: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.566: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.568: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.568: 130986562305: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.568: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.570: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.570: 130986564393: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.570: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.572: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.572: 130986566531: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.572: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.574: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.574: 130986568582: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.574: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.576: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.576: 130986570680: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.576: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.578: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.579: 130986572773: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.579: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.580: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.581: 130986574792: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.581: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.582: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.583: 130986576772: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.583: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.584: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.585: 130986578819: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.585: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.586: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.587: 130986580804: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.587: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.588: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.589: 130986582810: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.589: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.590: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.591: 130986584796: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.591: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.592: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.593: 130986586761: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.593: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.594: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.595: 130986588784: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.595: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.596: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.597: 130986591246: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.597: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.599: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.599: 130986593315: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.599: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.601: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.601: 130986595313: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.601: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.603: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.604: 130986598228: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.604: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.606: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.606: 130986600632: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.606: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.608: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.608: 130986602706: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.609: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.610: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.611: 130986604748: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.611: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.612: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.613: 130986606862: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.613: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.614: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.615: 130986608917: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.615: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.616: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.617: 130986610953: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.617: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.618: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.619: 130986613025: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.619: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.620: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.621: 130986615072: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.621: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.622: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.623: 130986617242: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.623: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.625: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.626: 130986619870: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.626: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.627: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.628: 130986622014: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.628: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.629: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.630: 130986624258: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.630: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.632: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.632: 130986626380: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.632: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.634: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.634: 130986628444: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.634: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.636: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.636: 130986630634: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.636: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.638: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.639: 130986632864: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.639: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.644: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.645: 130986638971: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.645: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.648: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.649: 130986643365: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.649: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.656: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.657: 130986651205: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.657: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.659: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.660: 130986654103: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.660: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.662: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.663: 130986657477: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.663: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.667: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.667: 130986661614: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.667: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.670: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.670: 130986664499: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.670: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.673: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.673: 130986667305: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.673: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.675: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.675: 130986669393: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.675: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.677: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.677: 130986671647: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.677: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.679: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.680: 130986673765: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.680: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.681: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.682: 130986676070: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.682: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.684: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.684: 130986678402: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.684: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.686: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.686: 130986680551: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.686: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.688: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.688: 130986682681: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.688: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.690: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.691: 130986684891: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.691: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.692: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.693: 130986687160: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.693: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.695: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.695: 130986689431: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.695: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.697: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.697: 130986691607: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.697: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.699: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.700: 130986694216: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.700: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.702: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.702: 130986696320: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.702: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.704: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.705: 130986698906: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.705: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.706: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.707: 130986701232: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.707: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.709: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.709: 130986703519: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.709: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.711: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.712: 130986706075: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.712: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.714: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.714: 130986708448: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.714: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.716: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.717: 130986710828: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.717: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.718: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.719: 130986713256: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.719: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.721: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.721: 130986715655: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.721: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.723: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.724: 130986717842: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.724: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.725: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.726: 130986719896: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.726: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.727: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.728: 130986722241: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.728: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.730: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.730: 130986724308: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.730: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.732: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.732: 130986726449: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.732: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.734: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.734: 130986728592: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.734: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.736: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.736: 130986730612: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.736: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.738: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.739: 130986732740: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.739: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.740: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.741: 130986735048: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.741: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.744: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.745: 130986739284: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.745: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.746: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.747: 130986741188: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.747: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.748: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.749: 130986743032: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.749: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.750: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.751: 130986744867: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.751: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.752: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.753: 130986746738: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.753: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.754: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.755: 130986748808: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.755: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.756: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.758: 130986751960: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.758: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.759: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.760: 130986754026: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.760: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.761: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.762: 130986755988: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.762: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.763: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.764: 130986757998: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.764: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.765: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.766: 130986759954: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.766: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.767: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.768: 130986762072: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.768: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.769: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.770: 130986764111: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.770: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.771: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.772: 130986766109: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.772: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.773: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.774: 130986768215: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.774: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.776: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.776: 130986770383: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.776: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.778: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.778: 130986772526: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.778: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.780: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.781: 130986774816: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.781: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.782: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.783: 130986776828: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.783: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.784: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.785: 130986778891: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.785: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.786: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.787: 130986780968: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.787: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.788: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.789: 130986783037: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.789: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.790: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.791: 130986785034: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.791: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.792: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.793: 130986787028: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.793: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.794: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.795: 130986789036: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.795: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.796: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.797: 130986791057: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.797: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.798: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.799: 130986793209: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.799: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.800: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.801: 130986795168: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.801: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.802: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.803: 130986797127: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.803: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.804: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.805: 130986799026: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.805: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.806: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.807: 130986800900: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.807: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.808: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.809: 130986802815: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.809: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.813: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.813: 130986807451: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.813: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.815: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.815: 130986809358: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.815: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.817: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.817: 130986811301: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.817: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.818: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.819: 130986813243: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.819: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.821: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.821: 130986815294: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.821: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.823: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.823: 130986817229: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.823: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.824: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.825: 130986819136: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.825: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.826: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.827: 130986821114: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.827: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.828: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.829: 130986823027: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.829: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.830: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.831: 130986825143: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.831: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.832: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.833: 130986827194: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.833: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.835: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.835: 130986829287: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.835: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.837: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.837: 130986831363: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.837: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.839: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.839: 130986833295: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.839: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.840: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.841: 130986835244: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.841: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.842: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.843: 130986837203: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.843: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.844: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.845: 130986839224: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.845: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.846: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.847: 130986841223: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.847: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.848: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.849: 130986843229: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.849: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.850: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.851: 130986845201: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.851: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.852: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.853: 130986847216: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.853: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.854: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.855: 130986849225: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.855: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.856: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.857: 130986851213: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.857: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.858: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.859: 130986853162: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.859: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.860: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.861: 130986855123: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.861: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.862: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.863: 130986857025: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.863: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.864: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.865: 130986858948: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.865: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.866: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.867: 130986860943: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.867: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.868: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.869: 130986862867: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.869: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.870: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.871: 130986864808: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.871: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.872: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.873: 130986866785: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.873: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.874: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.875: 130986868769: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.875: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.876: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.877: 130986870794: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.877: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.878: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.879: 130986872827: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.879: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.880: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.881: 130986874832: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.881: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.882: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.883: 130986876797: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.883: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.884: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.885: 130986878777: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.885: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.886: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.886: 130986880693: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.886: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.888: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.888: 130986882612: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.888: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.890: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.890: 130986884578: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.890: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.892: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.892: 130986886649: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.892: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.894: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.895: 130986888842: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.895: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.896: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.897: 130986891346: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.897: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.899: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.900: 130986893814: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.900: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.901: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.902: 130986895733: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.902: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.903: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.904: 130986898028: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.904: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.907: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.907: 130986901563: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.907: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.909: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.909: 130986903630: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.909: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.911: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.911: 130986905610: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.911: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.913: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.913: 130986907665: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.913: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.915: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.916: 130986909748: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.916: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.917: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.918: 130986912428: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.918: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.920: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.920: 130986914595: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.920: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.922: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.922: 130986916605: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.922: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.924: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.924: 130986918703: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.924: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.926: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.927: 130986920802: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.927: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.928: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.929: 130986923037: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.929: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.930: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.931: 130986924997: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.931: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.932: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.933: 130986927049: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.933: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.934: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.935: 130986929033: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.935: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.936: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.937: 130986930999: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.937: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.938: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.939: 130986933061: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.939: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.940: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.941: 130986935044: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.941: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.942: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.943: 130986937065: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.943: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.945: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.945: 130986939326: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.945: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.947: all registers written 407s Executing: libfprint-2/driver-aes2501.test 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.947: 130986941656: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.947: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.949: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.950: 130986943762: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.950: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.951: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.952: 130986945978: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.952: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.954: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.954: 130986948506: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.954: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.956: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.957: 130986950921: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.957: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.959: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.959: 130986953456: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.959: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.961: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.962: 130986955761: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.962: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.963: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.964: 130986958176: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.964: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.966: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.966: 130986960601: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.966: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.968: all registers written 407s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.969: 130986962965: ../libfprint/drivers/aes2501.c:310 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.969: write 23 regs 407s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.971: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.972: 130986965776: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.972: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.973: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.974: 130986968165: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.974: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.976: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.976: 130986970426: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.976: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.978: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.978: 130986972637: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.978: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.980: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.981: 130986974821: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.981: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.982: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.983: 130986977104: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.983: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.985: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.985: 130986979546: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.985: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.987: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.988: 130986981774: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.988: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.989: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.990: 130986984179: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.990: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.992: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.992: 130986986624: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.992: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.994: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.995: 130986988952: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.995: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.996: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:47.997: 130986991333: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.997: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:47.999: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.000: 130986993807: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.000: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.001: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.002: 130986996170: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.002: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.004: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.004: 130986998668: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.004: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.006: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.007: 130987001198: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.007: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.009: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.009: 130987003629: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.009: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.011: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.012: 130987005902: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.012: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.014: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.014: 130987008439: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.014: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.016: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.016: 130987010669: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.016: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.018: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.019: 130987013165: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.019: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.021: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.021: 130987015472: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.021: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.023: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.024: 130987017783: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.024: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.025: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.026: 130987020038: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.026: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.028: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.028: 130987022618: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.028: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.030: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.031: 130987024970: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.031: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.033: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.033: 130987027641: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.033: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.035: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.036: 130987030073: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.036: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.038: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.038: 130987032565: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.038: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.040: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.041: 130987034934: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.041: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.043: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.043: 130987037397: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.043: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.045: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.046: 130987039762: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.046: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.047: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.048: 130987042238: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.048: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.050: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.051: 130987044798: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.051: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.052: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.053: 130987047168: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.053: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.055: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.055: 130987049638: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.055: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.057: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.058: 130987052023: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.058: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.060: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.060: 130987054554: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.060: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.062: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.063: 130987056966: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.063: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.065: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.065: 130987059414: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.065: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.067: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.067: 130987061674: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.067: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.069: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.070: 130987064040: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.070: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.072: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.072: 130987066522: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.072: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.074: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.075: 130987069082: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.075: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.077: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.077: 130987071422: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.077: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.079: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.080: 130987073908: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.080: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.082: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.082: 130987076442: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.082: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.084: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.085: 130987078825: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.085: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.086: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.087: 130987081192: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.087: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.089: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.089: 130987083588: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.089: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.091: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.092: 130987086159: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.092: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.094: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.094: 130987088634: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.094: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.096: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.097: 130987091256: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.097: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.099: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.100: 130987093737: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.100: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.101: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.102: 130987096241: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.102: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.105: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.107: 130987100770: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.107: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.113: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.114: 130987107966: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.114: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.116: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.116: 130987110364: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.116: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.118: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.118: 130987112330: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.118: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.120: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.120: 130987114666: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.120: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.122: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.123: 130987116843: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.123: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.124: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.125: 130987118847: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.125: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.126: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.127: 130987120735: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.127: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.128: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.129: 130987122877: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.129: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.130: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.131: 130987124752: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.131: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.132: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.132: 130987126648: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.132: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.134: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.134: 130987128538: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.134: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.137: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.137: 130987131338: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.137: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.139: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.139: 130987133571: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.139: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.141: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.141: 130987135514: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.141: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.143: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.143: 130987137452: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.143: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.145: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.145: 130987139384: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.145: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.147: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.147: 130987141302: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.147: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.149: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.149: 130987143683: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.149: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.151: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.151: 130987145669: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.151: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.153: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.154: 130987147905: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.154: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.155: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.156: 130987149845: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.156: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.157: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.158: 130987151729: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.158: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.159: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.159: 130987153613: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.159: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.161: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.161: 130987155482: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.161: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.163: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.163: 130987157356: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.163: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.165: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.165: 130987159372: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.165: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.167: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.167: 130987161556: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.167: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.169: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.169: 130987163622: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.169: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.171: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.171: 130987165534: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.171: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.174: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.174: 130987168219: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.174: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.175: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.176: 130987170136: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.176: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.177: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.178: 130987172038: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.178: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.179: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.180: 130987174178: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.180: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.181: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.182: 130987176070: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.182: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.184: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.185: 130987178911: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.185: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.186: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.187: 130987180917: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.187: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.188: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.189: 130987182832: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.189: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.190: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.191: 130987184750: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.191: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.192: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.192: 130987186713: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.193: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.194: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.195: 130987188733: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.195: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.196: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.197: 130987191079: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.197: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.198: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.199: 130987193625: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.199: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.202: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.203: 130987197291: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.203: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.205: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.205: 130987199464: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.205: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.207: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.207: 130987201607: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.207: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.209: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.209: 130987203584: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.209: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.211: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.211: 130987205529: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.211: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.213: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.213: 130987207525: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.213: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.215: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.215: 130987209643: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.215: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.217: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.217: 130987211678: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.217: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.219: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.219: 130987213591: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.219: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.221: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.221: 130987215615: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.221: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.223: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.223: 130987217477: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.223: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.225: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.225: 130987219352: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.225: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.227: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.227: 130987221489: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.227: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.229: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.229: 130987223410: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.229: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.231: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.231: 130987225291: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.231: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.232: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.233: 130987227198: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.233: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.234: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.235: 130987229187: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.235: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.236: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.237: 130987231090: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.237: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.238: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.239: 130987233234: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.239: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.241: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.241: 130987235282: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.241: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.242: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.243: 130987237225: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.243: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.244: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.245: 130987239143: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.245: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.247: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.247: 130987241236: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.247: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.248: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.249: 130987243254: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.249: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.250: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.251: 130987245231: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.251: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.252: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.253: 130987247238: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.253: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.254: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.255: 130987249190: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.255: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.257: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.257: 130987251294: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.257: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.258: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.259: 130987253205: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.259: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.260: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.261: 130987255178: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.261: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.262: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.263: 130987257121: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.263: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.264: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.265: 130987259027: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.265: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.266: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.267: 130987260947: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.267: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.268: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.269: 130987262954: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.269: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.270: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.271: 130987264969: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.271: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.272: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.273: 130987266807: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.273: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.274: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.274: 130987268675: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.274: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.276: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.276: 130987270561: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.276: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.278: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.278: 130987272441: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.278: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.280: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.280: 130987274300: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.280: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.281: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.282: 130987276210: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.282: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.283: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.284: 130987278153: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.284: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.285: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.286: 130987280098: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.286: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.287: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.288: 130987282036: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.288: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.289: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.290: 130987283852: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.290: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.291: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.292: 130987285761: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.292: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.293: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.293: 130987287636: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.293: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.295: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.295: 130987289526: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.295: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.297: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.297: 130987291484: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.297: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.299: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.299: 130987293462: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.299: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.301: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.301: 130987295400: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.301: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.303: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.303: 130987297332: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.303: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.305: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.305: 130987299330: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.305: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.307: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.307: 130987301295: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.307: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.308: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.309: 130987303212: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.309: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.310: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.311: 130987305199: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.311: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.312: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.313: 130987307163: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.313: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.314: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.315: 130987309201: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.315: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.316: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.317: 130987311141: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.317: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.318: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.319: 130987313033: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.319: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.320: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.321: 130987315016: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.321: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.322: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.323: 130987316937: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.323: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.324: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.325: 130987318938: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.325: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.326: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.327: 130987320843: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.327: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.328: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.329: 130987322919: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.329: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.330: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.331: 130987324892: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.331: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.332: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.333: 130987326814: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.333: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.334: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.335: 130987328731: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.335: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.336: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.336: 130987330590: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.336: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.338: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.338: 130987332587: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.338: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.340: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.340: 130987334470: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.340: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.342: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.342: 130987336365: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.342: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.343: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.344: 130987338193: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.344: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.345: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.346: 130987340069: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.346: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.347: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.348: 130987341901: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.348: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.349: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.350: 130987343775: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.350: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.351: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.351: 130987345677: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.351: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.353: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.353: 130987347562: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.353: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.355: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.355: 130987349464: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.355: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.357: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.357: 130987351333: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.357: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.359: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.359: 130987353223: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.359: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.360: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.361: 130987355208: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.361: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.362: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.363: 130987357199: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.363: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.365: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.365: 130987359620: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.365: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.367: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.367: 130987361651: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.367: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.369: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.369: 130987363688: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.369: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.371: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.371: 130987365613: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.371: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.373: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.373: 130987367687: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.373: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.375: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.376: 130987369745: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.376: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.377: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.378: 130987371740: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.378: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.379: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.380: 130987373830: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.380: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.381: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.382: 130987375842: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.382: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.383: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.384: 130987377946: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.384: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.385: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.386: 130987379959: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.386: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.387: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.388: 130987381974: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.388: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.389: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.390: 130987384066: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.390: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.391: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.392: 130987386107: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.392: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.393: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.394: 130987388072: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.394: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.395: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.396: 130987390062: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.396: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.397: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.398: 130987392066: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.398: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.400: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.400: 130987394381: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.400: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.402: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.402: 130987396380: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.402: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.404: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.404: 130987398456: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.404: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.406: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.406: 130987400467: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.406: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.408: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.408: 130987402433: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.408: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.410: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.410: 130987404393: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.410: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.412: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.412: 130987406463: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.412: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.414: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.414: 130987408423: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.414: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.416: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.417: 130987410790: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.417: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.418: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.419: 130987412847: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.419: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.420: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.421: 130987414963: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.421: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.423: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.423: 130987417315: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.423: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.425: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.425: 130987419588: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.425: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.427: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.428: 130987421743: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.428: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.429: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.430: 130987423949: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.430: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.431: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.432: 130987426114: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.432: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.434: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.434: 130987428278: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.434: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.436: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.436: 130987430358: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.436: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.438: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.438: 130987432702: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.438: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.440: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.441: 130987435033: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.441: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.442: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.443: 130987437283: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.443: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.445: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.445: 130987439516: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.445: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.447: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.447: 130987441649: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.447: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.449: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.450: 130987443720: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.450: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.451: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.452: 130987445827: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.452: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.453: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.454: 130987448012: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.454: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.455: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.456: 130987450276: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.456: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.458: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.458: 130987452456: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.458: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.460: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.460: 130987454651: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.460: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.462: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.463: 130987456795: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.463: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.464: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.465: 130987459141: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.465: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.467: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.467: 130987461338: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.467: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.469: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.469: 130987463634: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.469: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.471: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.472: 130987465869: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.472: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.473: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.474: 130987468010: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.474: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.475: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.476: 130987470181: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.476: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.478: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.478: 130987472384: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.478: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.480: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.480: 130987474584: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.480: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.482: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.482: 130987476681: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.482: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.484: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.485: 130987478776: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.485: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.486: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.487: 130987480915: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.487: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.488: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.489: 130987483037: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.489: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.490: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.491: 130987485208: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.491: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.493: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.493: 130987487381: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.493: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.495: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.495: 130987489450: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.495: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.497: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.497: 130987491590: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.497: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.499: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.499: 130987493694: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.499: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.501: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.502: 130987495914: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.502: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.503: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.504: 130987498040: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.504: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.505: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.506: 130987500231: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.506: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.508: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.508: 130987502419: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.508: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.510: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.510: 130987504468: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.510: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.512: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.512: 130987506555: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.512: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.514: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.515: 130987508727: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.515: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.516: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.517: 130987510882: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.517: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.518: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.519: 130987513070: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.519: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.520: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.521: 130987515179: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.521: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.523: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.523: 130987517324: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.523: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.525: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.525: 130987519450: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.525: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.527: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.527: 130987521685: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.527: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.529: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.530: 130987523831: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.530: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.531: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.532: 130987526016: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.532: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.533: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.534: 130987528226: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.534: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.536: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.536: 130987530468: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.536: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.538: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.538: 130987532695: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.538: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.540: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.541: 130987534829: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.541: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.542: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.543: 130987536861: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.543: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.544: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.545: 130987538986: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.545: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.546: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.547: 130987541036: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.547: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.548: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.549: 130987543130: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.549: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.551: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.551: 130987545306: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.551: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.553: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.553: 130987547489: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.553: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.555: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.555: 130987549663: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.555: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.557: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.558: 130987551858: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.558: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.559: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.560: 130987553996: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.560: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.561: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.562: 130987556192: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.562: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.564: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.564: 130987558313: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.564: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.566: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.566: 130987560393: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.566: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.568: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.568: 130987562481: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.568: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.570: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.571: 130987564748: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.571: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.572: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.573: 130987566988: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.573: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.574: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.575: 130987569180: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.575: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.577: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.577: 130987571399: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.577: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.579: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.579: 130987573537: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.579: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.581: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.582: 130987575721: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.582: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.583: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.584: 130987577824: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.584: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.585: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.586: 130987579983: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.586: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.588: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.588: 130987582398: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.588: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.590: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.590: 130987584565: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.590: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.592: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.593: 130987586747: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.593: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.594: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.595: 130987588781: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.595: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.596: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.597: 130987590868: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.597: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.598: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.599: 130987593016: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.599: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.600: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.601: 130987595146: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.601: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.603: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.603: 130987597308: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.603: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.605: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.605: 130987599548: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.605: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.607: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.607: 130987601632: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.607: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.609: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.610: 130987603790: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.610: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.611: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.612: 130987606013: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.612: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.613: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.614: 130987608128: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.614: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.616: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.616: 130987610309: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.616: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.618: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.618: 130987612548: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.618: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.620: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.620: 130987614664: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.620: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.622: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.623: 130987616788: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.623: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.624: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.625: 130987618954: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.625: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.626: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.627: 130987621209: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.627: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.629: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.629: 130987623434: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.629: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.631: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.632: 130987626214: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.632: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.634: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.635: 130987628849: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.635: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.636: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.637: 130987631305: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.637: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.639: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.640: 130987633818: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.640: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.641: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.642: 130987635992: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.642: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.643: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.644: 130987638152: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.644: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.645: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.646: 130987640308: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.646: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.648: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.648: 130987642469: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.648: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.650: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.650: 130987644718: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.651: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.652: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.653: 130987647080: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.653: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.655: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.655: 130987649607: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.655: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.657: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.658: 130987651899: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.658: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.659: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.660: 130987654136: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.660: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.662: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.663: 130987657126: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.663: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.665: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.666: 130987659827: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.666: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.668: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.668: 130987662508: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.668: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.670: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.670: 130987664604: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.670: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.672: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.673: 130987666746: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.673: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.674: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.675: 130987668902: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.675: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.676: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.677: 130987671067: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.677: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.678: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.679: 130987673284: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.679: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.681: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.681: 130987675387: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.681: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.683: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.683: 130987677477: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.683: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.685: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.685: 130987679620: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.685: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.687: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.688: 130987681790: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.688: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.689: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.690: 130987684038: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.690: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.691: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.692: 130987686304: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.692: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.694: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.694: 130987688322: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.694: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.696: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.696: 130987690464: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.696: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.698: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.698: 130987692564: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.698: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.700: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.700: 130987694706: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.700: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.702: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.703: 130987696782: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.703: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.704: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.705: 130987698834: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.705: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.706: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.707: 130987700973: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.707: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.708: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.709: 130987703255: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.709: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.711: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.711: 130987705422: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.711: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.713: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.713: 130987707582: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.713: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.715: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.716: 130987709859: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.716: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.717: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.718: 130987711949: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.718: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.719: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.720: 130987714087: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.720: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.721: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.722: 130987716202: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.722: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.724: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.724: 130987718453: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.724: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.726: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.726: 130987720640: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.726: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.728: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.729: 130987722806: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.729: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.730: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.731: 130987724866: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.731: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.732: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.733: 130987727051: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.733: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.734: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.735: 130987729198: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.735: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.737: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.737: 130987731309: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.737: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.739: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.739: 130987733521: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.739: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.741: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.741: 130987735699: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.741: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.743: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.744: 130987737804: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.744: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.745: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.746: 130987739934: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.746: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.747: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.748: 130987742132: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.748: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.749: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.750: 130987744206: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.750: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.752: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.752: 130987746204: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.752: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.754: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.754: 130987748259: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.754: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.756: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.756: 130987750453: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.756: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.758: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.759: 130987753051: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.759: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.760: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.761: 130987755135: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.761: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.762: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.763: 130987757282: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.763: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.765: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.765: 130987759396: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.765: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.767: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.767: 130987761512: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.767: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.769: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.769: 130987763684: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.769: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.771: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.772: 130987765845: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.772: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.773: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.774: 130987768077: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.774: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.775: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.776: 130987770224: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.776: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.778: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.778: 130987772374: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.778: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.780: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.780: 130987774451: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.780: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.782: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.782: 130987776508: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.782: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.784: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.784: 130987778654: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.784: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.786: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.787: 130987780774: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.787: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.788: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.789: 130987782855: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.789: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.790: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.791: 130987784966: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.791: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.792: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.793: 130987786970: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.793: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.794: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.795: 130987789038: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.795: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.796: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.797: 130987791184: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.797: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.799: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.799: 130987793326: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.799: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.801: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.801: 130987795463: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.801: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.803: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.803: 130987797682: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.803: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.805: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.806: 130987800178: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.806: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.808: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.808: 130987802683: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.808: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.810: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.811: 130987805208: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.811: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.813: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.813: 130987807702: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.813: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.815: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.816: 130987810132: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.816: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.818: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.818: 130987812635: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.818: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.820: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.821: 130987814917: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.821: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.822: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.823: 130987817234: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.823: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.825: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.825: 130987819696: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.825: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.827: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.828: 130987822149: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.828: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.830: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.830: 130987824443: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.830: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.832: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.833: 130987826738: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.833: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.834: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.835: 130987829149: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.835: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.837: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.837: 130987831344: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.837: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.839: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.840: 130987833900: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.840: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.841: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.842: 130987836145: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.842: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.844: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.844: 130987838492: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.844: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.846: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.846: 130987840697: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.846: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.848: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.849: 130987843191: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.849: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.851: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.851: 130987845599: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.851: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.853: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.854: 130987847943: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.854: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.856: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.856: 130987850347: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.856: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.858: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.859: 130987852745: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.859: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.860: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.861: 130987855152: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.861: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.863: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.863: 130987857519: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.863: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.865: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.866: 130987859893: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.866: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.867: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.868: 130987862210: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.868: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.870: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.870: 130987864646: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.870: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.872: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.873: 130987867048: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.873: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.875: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.875: 130987869404: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.875: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.877: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.878: 130987871781: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.878: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.879: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.880: 130987874051: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.880: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.881: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.882: 130987876322: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.882: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.884: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.885: 130987878849: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.885: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.886: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.887: 130987881307: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.887: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.889: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.889: 130987883675: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.889: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.891: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.892: 130987886055: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.892: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.893: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.894: 130987888314: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.894: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.896: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.896: 130987890600: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.896: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.898: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.899: 130987892971: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.899: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.901: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.901: 130987895501: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.901: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.903: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.904: 130987897837: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.904: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.905: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.906: 130987900247: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.906: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.908: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.909: 130987902891: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.909: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.911: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.911: 130987905439: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.911: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.913: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.914: 130987907952: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.914: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.916: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.916: 130987910493: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.916: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.918: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.919: 130987912899: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.919: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.920: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.921: 130987915233: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.921: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.923: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.924: 130987917733: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.924: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.925: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.926: 130987920255: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.926: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.928: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.928: 130987922661: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.928: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.930: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.931: 130987924990: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.931: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.932: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.933: 130987927291: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.933: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.935: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.935: 130987929617: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.935: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.937: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.938: 130987932054: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.938: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.940: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.940: 130987934428: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.940: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.942: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.943: 130987936848: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.943: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.944: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.945: 130987939171: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.945: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.947: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.947: 130987941583: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.947: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.949: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.950: 130987943998: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.950: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.952: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.952: 130987946389: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.952: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.954: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.955: 130987948789: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.955: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.956: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.957: 130987951135: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.957: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.959: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.959: 130987953433: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.959: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.961: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.962: 130987956019: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.962: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.963: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.964: 130987958029: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.964: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.965: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.966: 130987960156: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.966: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.967: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.968: 130987962139: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.968: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.969: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.970: 130987964166: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.970: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.972: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.972: 130987966618: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.972: write 23 regs 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.974: all registers written 408s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.975: 130987968720: ../libfprint/drivers/aes2501.c:310 408s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.975: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.976: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.977: 130987970794: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.977: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.978: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.979: 130987972805: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.979: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.980: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.981: 130987974841: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.981: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.982: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.983: 130987976908: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.983: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.984: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.985: 130987978943: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.985: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.986: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.987: 130987981034: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.987: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.988: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.989: 130987983122: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.989: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.991: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.991: 130987985307: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.991: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.993: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.993: 130987987402: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.993: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.995: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.995: 130987989526: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.995: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.997: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:48.997: 130987991631: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.997: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:48.999: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.000: 130987993737: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.000: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.001: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.002: 130987995879: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.002: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.003: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.004: 130987998074: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.004: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.005: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.006: 130988000155: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.006: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.007: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.008: 130988002172: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.008: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.009: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.010: 130988004185: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.010: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.012: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.012: 130988006335: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.012: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.014: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.014: 130988008478: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.014: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.016: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.016: 130988010516: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.016: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.018: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.018: 130988012582: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.018: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.020: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.020: 130988014591: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.020: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.022: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.022: 130988016705: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.023: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.024: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.025: 130988018826: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.025: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.026: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.027: 130988020857: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.027: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.028: all registers written 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.029: 130988022918: ../libfprint/drivers/aes2501.c:310 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.029: write 23 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.030: all registers written 409s (process:2027): libfprint-device-DEBUG: 05:08:49.031: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 409s (process:2027): libfprint-image_device-DEBUG: 05:08:49.031: Image device reported finger status: on 409s (process:2027): libfprint-image_device-DEBUG: 05:08:49.031: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.031: 130988025013: ../libfprint/drivers/aes2501.c:581 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.031: [aes2501] CAPTURE_NUM_STATES entering state 0 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.031: write 26 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.032: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.032: [aes2501] CAPTURE_NUM_STATES entering state 1 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.033: [aes2501] CAPTURE_NUM_STATES entering state 2 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.033: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.033: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.033: [aes2501] CAPTURE_NUM_STATES entering state 3 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.034: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.034: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.034: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.034: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.035: sum=5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.035: ADREFHI is 50 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.035: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.035: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.036: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.036: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.036: sum=8 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.036: ADREFHI is 48 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.036: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.036: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.037: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.037: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.037: sum=19 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.037: ADREFHI is 40 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.037: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.037: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.038: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.038: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.039: sum=60 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.039: ADREFHI is 38 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.039: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.039: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.039: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.039: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.040: sum=123 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.040: ADREFHI is 30 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.040: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.040: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.040: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.040: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.041: sum=226 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.041: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.041: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.041: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.041: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.041: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.042: sum=461 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.042: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.042: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.042: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.042: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.042: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.043: sum=466 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.043: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.043: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.043: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.043: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.043: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.044: sum=465 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.044: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.044: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.044: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.044: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.044: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.045: sum=620 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.045: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.045: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.045: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.045: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.045: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.046: sum=629 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.046: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.046: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.046: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.047: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.047: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.047: sum=615 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.047: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.047: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.047: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.048: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.048: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.048: sum=585 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.048: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.048: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.048: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.049: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.049: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.049: sum=581 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.049: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.049: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.049: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.050: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.050: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.051: sum=418 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.051: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.051: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.051: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.051: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.051: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.052: sum=406 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.052: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.052: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.052: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.052: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.052: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.053: sum=389 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.053: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.053: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.053: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.053: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.053: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.054: sum=388 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.054: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.054: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.054: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.054: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.054: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.055: sum=393 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.055: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.055: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.055: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.056: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.056: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.056: sum=389 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.056: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.056: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.056: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.057: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.057: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.058: sum=379 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.058: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.058: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.058: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.058: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.058: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.059: sum=361 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.059: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.059: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.059: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.060: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.060: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.060: sum=356 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.060: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.060: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.060: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.061: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.061: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.061: sum=193 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.061: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.061: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.061: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.062: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.062: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.063: sum=178 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.063: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.063: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.063: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.063: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.063: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.064: sum=164 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.064: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.064: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.064: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.064: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.064: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.065: sum=157 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.065: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.065: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.065: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.065: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.065: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.066: sum=152 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.066: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.066: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.066: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.066: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.067: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.067: sum=154 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.067: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.067: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.067: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.068: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.068: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.068: sum=157 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.068: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.068: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.068: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.069: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.069: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.069: sum=161 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.069: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.069: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.069: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.070: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.070: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.070: sum=161 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.070: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.070: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.070: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.071: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.071: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.071: sum=161 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.072: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.072: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.072: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.072: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.072: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.073: sum=162 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.073: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.073: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.073: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.073: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.073: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.074: sum=166 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.074: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.074: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.074: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.074: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.074: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.075: sum=143 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.075: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.075: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.075: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.076: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.076: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.076: sum=106 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.076: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.076: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.076: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.077: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.077: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.077: sum=74 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.077: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.077: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.077: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.078: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.078: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.078: sum=51 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.078: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.078: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.078: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.079: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.079: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.079: sum=40 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.079: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.079: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.079: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.080: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.080: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.080: sum=39 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.080: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.080: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.080: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.081: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.081: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.082: sum=19 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.082: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.082: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.082: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.082: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.082: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.083: sum=13 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.083: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.083: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.083: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.083: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.083: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.084: sum=5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.084: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.084: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.084: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.084: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.084: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.085: sum=2 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.085: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.085: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.085: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.085: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.085: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.086: sum=0 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.086: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.086: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.086: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.086: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.086: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.087: sum=0 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.087: ADREFHI is 28 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.087: [aes2501] CAPTURE_NUM_STATES entering state 4 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.087: write 7 regs 409s (process:2027): libfprint-aeslib-DEBUG: 05:08:49.087: all registers written 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.087: [aes2501] CAPTURE_NUM_STATES entering state 5 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.088: sum=0 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.088: ADREFHI is 28 409s (process:2027): libfprint-assembling-DEBUG: 05:08:49.200: calc delta completed in 0.111915 secs 409s (process:2027): libfprint-assembling-DEBUG: 05:08:49.312: calc delta completed in 0.112383 secs 409s (process:2027): libfprint-assembling-DEBUG: 05:08:49.312: errors: 53228 rev: 72653 409s (process:2027): libfprint-assembling-DEBUG: 05:08:49.424: calc delta completed in 0.111934 secs 409s (process:2027): libfprint-assembling-DEBUG: 05:08:49.424: height is 102 409s (process:2027): libfprint-image_device-DEBUG: 05:08:49.425: Image device captured an image 409s (process:2027): libfprint-image_device-DEBUG: 05:08:49.426: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 409s (process:2027): libfprint-device-DEBUG: 05:08:49.426: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2027): libfprint-device-DEBUG: 05:08:49.426: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2027): libfprint-image_device-DEBUG: 05:08:49.426: Image device reported finger status: off 409s (process:2027): libfprint-image_device-DEBUG: 05:08:49.426: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 409s (process:2027): libfprint-image_device-DEBUG: 05:08:49.426: Deactivating image device 409s (process:2027): libfprint-image_device-DEBUG: 05:08:49.426: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 409s (process:2027): libfprint-SSM-DEBUG: 05:08:49.426: [aes2501] CAPTURE_NUM_STATES completed successfully 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.426: 130988420611: ../libfprint/drivers/aes2501.c:547 409s (process:2027): libfprint-aes2501-DEBUG: 05:08:49.426: 130988420616: ../libfprint/drivers/aes2501.c:820 409s (process:2027): libfprint-image_device-DEBUG: 05:08:49.426: Image device deactivation completed 409s (process:2027): libfprint-image_device-DEBUG: 05:08:49.426: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 409s (process:2027): libfprint-image-DEBUG: 05:08:49.432: Minutiae scan completed in 0.005553 secs 409s (process:2027): libfprint-device-DEBUG: 05:08:49.432: Device reported capture completion 409s (process:2027): libfprint-device-DEBUG: 05:08:49.432: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 409s (process:2027): libfprint-device-DEBUG: 05:08:49.432: Updated temperature model after 1.89 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 409s (process:2027): libfprint-image_device-DEBUG: 05:08:49.433: Image device close completed 409s (process:2027): libfprint-device-DEBUG: 05:08:49.433: Device reported close completion 409s (process:2027): libfprint-device-DEBUG: 05:08:49.433: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 409s (process:2027): libfprint-device-DEBUG: 05:08:49.433: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 409s ** (umockdev-run:2023): DEBUG: 05:08:49.505: umockdev.vala:154: Removing test bed /tmp/umockdev.RW1F22 409s (umockdev-run:2023): GLib-DEBUG: 05:08:49.511: unsetenv() is not thread-safe and should not be used after threads are created 409s Comparing PNGs /tmp/libfprint-umockdev-test-mu24ve9x/capture.png and /usr/share/installed-tests/libfprint-2/aes2501/capture.png 409s PASS: libfprint-2/driver-aes2501.test 409s Running test: libfprint-2/driver-realtek.test 409s ** (umockdev-run:2036): DEBUG: 05:08:49.583: umockdev.vala:127: Created udev test bed /tmp/umockdev.WL3112 409s ** (umockdev-run:2036): DEBUG: 05:08:49.583: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-8 409s ** (umockdev-run:2036): DEBUG: 05:08:49.585: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-8 (subsystem usb) 409s ** (umockdev-run:2036): DEBUG: 05:08:49.590: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WL3112/dev/bus/usb/001/025 409s ** (umockdev-run:2036): DEBUG: 05:08:49.590: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 409s ** (umockdev-run:2036): DEBUG: 05:08:49.592: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 409s ** (umockdev-run:2036): DEBUG: 05:08:49.596: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WL3112/dev/bus/usb/001/001 409s ** (umockdev-run:2036): DEBUG: 05:08:49.596: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 409s ** (umockdev-run:2036): DEBUG: 05:08:49.597: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 409s (process:2040): libfprint-context-DEBUG: 05:08:49.708: Initializing FpContext (libfprint version 1.94.9+tod1) 409s (process:2040): libfprint-tod-DEBUG: 05:08:49.708: 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:2040): libfprint-context-DEBUG: 05:08:49.711: No driver found for USB device 1D6B:0002 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.712: 130988705804: ../libfprint/drivers/realtek/realtek.c:1224 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.714: Device name: Realtek USB2.0 Finger Print Bridge 409s (process:2040): libfprint-device-DEBUG: 05:08:49.715: Device reported probe completion 409s (process:2040): libfprint-device-DEBUG: 05:08:49.715: Completing action FPI_DEVICE_ACTION_PROBE in idle! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.715: Not updating temperature model, device can run continuously! 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.716: 130988710297: ../libfprint/drivers/realtek/realtek.c:1269 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.717: [realtek] Init entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.717: [realtek] Init entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.717: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.718: [realtek] Init entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.719: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.720: [realtek] Init completed successfully 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.720: Init complete! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.720: Device reported open completion 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.720: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-device-DEBUG: 05:08:49.720: Completing action FPI_DEVICE_ACTION_OPEN in idle! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.720: Not updating temperature model, device can run continuously! 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.720: 130988714309: ../libfprint/drivers/realtek/realtek.c:1332 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.720: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.721: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.721: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.721: Successfully cleared storage 409s (process:2040): libfprint-device-DEBUG: 05:08:49.721: Device reported deletion completion 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.721: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-device-DEBUG: 05:08:49.721: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.721: Not updating temperature model, device can run continuously! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.722: Not updating temperature model, device can run continuously! 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.722: 130988716619: ../libfprint/drivers/realtek/realtek.c:1201 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.722: [realtek] Enroll entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.722: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.723: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.724: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.724: [realtek] Enroll entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.724: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.724: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.725: [realtek] Enroll entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.725: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.726: [realtek] Enroll entering state 3 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.726: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.727: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.727: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.728: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.728: [realtek] Enroll entering state 4 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.728: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.729: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2040): libfprint-device-DEBUG: 05:08:49.729: Device reported enroll progress, reported 1 of 8 have been completed 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.729: [realtek] Enroll entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.729: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.730: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.730: [realtek] Enroll entering state 3 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.731: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.732: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.732: [realtek] Enroll entering state 4 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.732: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.732: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.734: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2040): libfprint-device-DEBUG: 05:08:49.734: Device reported enroll progress, reported 2 of 8 have been completed 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.734: [realtek] Enroll entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.734: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.734: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.735: [realtek] Enroll entering state 3 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.735: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.736: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.736: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.736: [realtek] Enroll entering state 4 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.736: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.737: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.737: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.738: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.738: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2040): libfprint-device-DEBUG: 05:08:49.738: Device reported enroll progress, reported 3 of 8 have been completed 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.738: [realtek] Enroll entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.738: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.738: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.739: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.739: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.739: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.739: [realtek] Enroll entering state 3 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.739: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.740: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.740: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.740: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.741: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.741: [realtek] Enroll entering state 4 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.741: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.741: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.741: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.742: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.743: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2040): libfprint-device-DEBUG: 05:08:49.743: Device reported enroll progress, reported 4 of 8 have been completed 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.743: [realtek] Enroll entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.743: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.743: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.743: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.743: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.743: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.744: [realtek] Enroll entering state 3 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.744: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.744: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.744: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.745: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.746: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.746: [realtek] Enroll entering state 4 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.746: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.746: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.746: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.747: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.747: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2040): libfprint-device-DEBUG: 05:08:49.747: Device reported enroll progress, reported 5 of 8 have been completed 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.747: [realtek] Enroll entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.747: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.747: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.748: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.748: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.748: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.748: [realtek] Enroll entering state 3 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.748: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.749: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.749: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.750: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.750: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.750: [realtek] Enroll entering state 4 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.750: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.750: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.751: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.751: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.752: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2040): libfprint-device-DEBUG: 05:08:49.752: Device reported enroll progress, reported 6 of 8 have been completed 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.752: [realtek] Enroll entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.752: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.752: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.752: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.752: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.752: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.753: [realtek] Enroll entering state 3 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.753: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.753: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.754: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.754: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.755: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.755: [realtek] Enroll entering state 4 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.755: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.755: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.755: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.756: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.756: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2040): libfprint-device-DEBUG: 05:08:49.756: Device reported enroll progress, reported 7 of 8 have been completed 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.756: [realtek] Enroll entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.756: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.756: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.757: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.757: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.757: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.758: [realtek] Enroll entering state 3 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.758: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.758: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.758: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.759: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.759: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.759: [realtek] Enroll entering state 4 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.759: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.759: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.760: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.760: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.761: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2040): libfprint-device-DEBUG: 05:08:49.761: Device reported enroll progress, reported 8 of 8 have been completed 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.761: [realtek] Enroll entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.761: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.761: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.761: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.761: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.761: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.762: [realtek] Enroll entering state 3 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.762: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.762: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.763: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.763: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.764: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.764: [realtek] Enroll entering state 4 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.764: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.764: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.764: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.765: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.765: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.765: [realtek] Enroll entering state 5 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.765: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.766: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.766: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.767: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.767: [realtek] Enroll entering state 6 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.767: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.767: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.767: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.768: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.768: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.769: [realtek] Enroll completed successfully 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.769: Enrollment complete! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.769: Device reported enroll completion 409s (process:2040): libfprint-device-DEBUG: 05:08:49.769: Print for finger FP_FINGER_UNKNOWN enrolled 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.769: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-device-DEBUG: 05:08:49.769: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.769: Not updating temperature model, device can run continuously! 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.769: 130988763246: ../libfprint/drivers/realtek/realtek.c:1344 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.769: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.770: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.770: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.771: Query templates complete! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.771: Device reported listing completion 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.771: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-device-DEBUG: 05:08:49.771: Completing action FPI_DEVICE_ACTION_LIST in idle! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.771: Not updating temperature model, device can run continuously! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.771: Not updating temperature model, device can run continuously! 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.771: 130988765249: ../libfprint/drivers/realtek/realtek.c:1177 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.771: [realtek] Verify & Identify entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.771: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.772: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.772: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.773: [realtek] Verify & Identify entering state 1 409s (process:2040): libfprint-device-DEBUG: 05:08:49.773: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.773: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.773: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.773: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.773: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.774: [realtek] Verify & Identify entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.774: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.774: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.775: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.775: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.776: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.776: [realtek] Verify & Identify entering state 3 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.776: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.776: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.776: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.777: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.778: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.778: [realtek] Verify & Identify entering state 4 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.778: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.778: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.778: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.779: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.779: Device reported verify result 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.779: [realtek] Verify & Identify entering state 5 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.779: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.779: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.780: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.780: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.780: [realtek] Verify & Identify completed successfully 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.780: Verify complete! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.780: Device reported verify completion 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.780: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-device-DEBUG: 05:08:49.780: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.780: Not updating temperature model, device can run continuously! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.781: Not updating temperature model, device can run continuously! 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.781: 130988775035: ../libfprint/drivers/realtek/realtek.c:1177 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.781: [realtek] Verify & Identify entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.781: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.781: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.782: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.782: [realtek] Verify & Identify entering state 1 409s (process:2040): libfprint-device-DEBUG: 05:08:49.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.782: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.783: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.783: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.783: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.783: [realtek] Verify & Identify entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.783: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.784: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.784: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.784: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.785: Device reported finger status change: FP_FINGER_STATUS_PRESENT 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.785: [realtek] Verify & Identify entering state 3 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.785: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.785: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.786: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.786: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.787: Device reported finger status change: FP_FINGER_STATUS_NONE 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.787: [realtek] Verify & Identify entering state 4 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.787: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.787: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.787: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.788: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-device-DEBUG: 05:08:49.788: Device reported identify result 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.788: [realtek] Verify & Identify completed successfully 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.788: Verify complete! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.788: Device reported identify completion 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.788: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-device-DEBUG: 05:08:49.788: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.788: Not updating temperature model, device can run continuously! 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.789: 130988782947: ../libfprint/drivers/realtek/realtek.c:1313 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.789: [realtek] Delete print entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.789: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.789: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.790: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.790: [realtek] Delete print entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.790: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.791: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.791: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.791: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.791: [realtek] Delete print completed successfully 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.791: Delete print complete! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.791: Device reported deletion completion 409s (process:2040): libfprint-SSM-DEBUG: 05:08:49.791: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 409s (process:2040): libfprint-device-DEBUG: 05:08:49.791: Completing action FPI_DEVICE_ACTION_DELETE in idle! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.791: Not updating temperature model, device can run continuously! 409s (process:2040): libfprint-realtek-DEBUG: 05:08:49.792: 130988785793: ../libfprint/drivers/realtek/realtek.c:1301 409s (process:2040): libfprint-device-DEBUG: 05:08:49.792: Device reported close completion 409s (process:2040): libfprint-device-DEBUG: 05:08:49.792: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 409s (process:2040): libfprint-device-DEBUG: 05:08:49.792: Not updating temperature model, device can run continuously! 409s enrolling 409s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea8f06c8 (FpiDeviceRealtek at 0x195e9a8)>, 1, None, None, None) 409s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea8f06c8 (FpiDeviceRealtek at 0x195e9a8)>, 2, None, None, None) 409s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea8f06c8 (FpiDeviceRealtek at 0x195e9a8)>, 3, None, None, None) 409s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea8f06c8 (FpiDeviceRealtek at 0x195e9a8)>, 4, None, None, None) 409s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea8f06c8 (FpiDeviceRealtek at 0x195e9a8)>, 5, None, None, None) 409s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea8f06c8 (FpiDeviceRealtek at 0x195e9a8)>, 6, None, None, None) 409s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea8f06c8 (FpiDeviceRealtek at 0x195e9a8)>, 7, None, None, None) 409s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xea8f06c8 (FpiDeviceRealtek at 0x195e9a8)>, 8, 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:2036): DEBUG: 05:08:49.817: umockdev.vala:154: Removing test bed /tmp/umockdev.WL3112 409s (umockdev-run:2036): GLib-DEBUG: 05:08:49.824: unsetenv() is not thread-safe and should not be used after threads are created 409s PASS: libfprint-2/driver-realtek.test 409s Running test: libfprint-2/driver-goodixmoc.test 409s ** (umockdev-run:2048): DEBUG: 05:08:49.880: umockdev.vala:127: Created udev test bed /tmp/umockdev.DGK512 409s ** (umockdev-run:2048): DEBUG: 05:08:49.880: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-9 409s ** (umockdev-run:2048): DEBUG: 05:08:49.882: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-9 (subsystem usb) 409s ** (umockdev-run:2048): DEBUG: 05:08:49.886: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DGK512/dev/bus/usb/003/004 409s ** (umockdev-run:2048): DEBUG: 05:08:49.887: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 409s ** (umockdev-run:2048): DEBUG: 05:08:49.888: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 409s ** (umockdev-run:2048): DEBUG: 05:08:49.893: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DGK512/dev/bus/usb/003/001 409s ** (umockdev-run:2048): DEBUG: 05:08:49.893: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 409s ** (umockdev-run:2048): DEBUG: 05:08:49.893: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 410s (process:2052): libfprint-context-DEBUG: 05:08:50.001: Initializing FpContext (libfprint version 1.94.9+tod1) 410s (process:2052): libfprint-tod-DEBUG: 05:08:50.001: 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:2052): libfprint-context-DEBUG: 05:08:50.004: No driver found for USB device 1D6B:0002 410s (process:2052): libfprint-device-DEBUG: 05:08:50.006: Device reported probe completion 410s (process:2052): libfprint-device-DEBUG: 05:08:50.006: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.006: Not updating temperature model, device can run continuously! 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.007: [goodixmoc] FP_INIT_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.007: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.008: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.008: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.009: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.009: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-goodixmoc-DEBUG: 05:08:50.010: Firmware type: APP 410s (process:2052): libfprint-goodixmoc-DEBUG: 05:08:50.010: Firmware version: 01000274 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.010: [goodixmoc] FP_INIT_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.010: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.010: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.010: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.011: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.011: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.012: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.012: [goodixmoc] FP_INIT_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.012: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.012: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.013: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.013: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.014: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.014: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.015: [goodixmoc] FP_INIT_NUM_STATES completed successfully 410s (process:2052): libfprint-device-DEBUG: 05:08:50.015: Device reported open completion 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.015: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-device-DEBUG: 05:08:50.015: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.015: Not updating temperature model, device can run continuously! 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.015: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.015: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.016: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.016: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.017: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-goodixmoc-DEBUG: 05:08:50.017: Successfully cleared storage 410s (process:2052): libfprint-device-DEBUG: 05:08:50.017: Device reported deletion completion 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.017: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-device-DEBUG: 05:08:50.017: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.017: Not updating temperature model, device can run continuously! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.018: Not updating temperature model, device can run continuously! 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.018: [goodixmoc] enroll entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.018: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.019: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.019: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.020: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.020: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.021: [goodixmoc] enroll entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.021: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.021: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.021: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.022: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.022: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.023: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.023: [goodixmoc] enroll entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.023: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.023: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.024: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.024: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.025: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.025: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.026: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-device-DEBUG: 05:08:50.026: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.026: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.026: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.026: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.027: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.027: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.028: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.028: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.028: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.028: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.028: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.029: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.029: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.029: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.030: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.030: Device reported enroll progress, reported 1 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.031: [goodixmoc] enroll entering state 5 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.031: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.031: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.031: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.032: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.032: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.033: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.033: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.033: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.033: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.033: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.034: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.034: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.035: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.035: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.036: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.036: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.036: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.036: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.037: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.037: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.037: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.038: Device reported enroll progress, reported 2 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.038: [goodixmoc] enroll entering state 5 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.038: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.038: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.039: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.039: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.040: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.040: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.041: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.041: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.041: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.041: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.041: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.042: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.042: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.043: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.043: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.043: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.043: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.043: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.044: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.044: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.045: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.045: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.046: Device reported enroll progress, reported 3 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.046: [goodixmoc] enroll entering state 5 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.046: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.046: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.046: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.047: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.047: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.048: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.048: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.048: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.048: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.048: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.049: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.049: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.052: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.054: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.055: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.055: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.055: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.056: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.056: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.057: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.058: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.058: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.059: Device reported enroll progress, reported 4 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.059: [goodixmoc] enroll entering state 5 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.059: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.059: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.059: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.060: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.061: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.061: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.062: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.062: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.063: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.063: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.063: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.064: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.064: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.065: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.065: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.065: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.065: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.066: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.066: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.067: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.067: Device reported enroll progress, reported 5 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.067: [goodixmoc] enroll entering state 5 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.067: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.067: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.068: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.068: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.069: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.069: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.070: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.070: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.070: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.070: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.071: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.071: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.072: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.072: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.072: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.072: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.072: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.073: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.073: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.074: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.074: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.075: Device reported enroll progress, reported 6 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.075: [goodixmoc] enroll entering state 5 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.075: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.075: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.075: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.076: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.076: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.077: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.077: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.077: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.077: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.078: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.078: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.078: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.079: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.079: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.080: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.080: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.080: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.080: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.081: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.082: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.083: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.084: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.084: Device reported enroll progress, reported 7 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.084: [goodixmoc] enroll entering state 5 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.084: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.085: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.085: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.085: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.086: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.087: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.088: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.088: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.088: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.088: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.089: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.090: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.090: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.091: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.091: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.091: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.091: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.091: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.092: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.093: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.093: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.094: Device reported enroll progress, reported 8 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.094: [goodixmoc] enroll entering state 5 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.094: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.095: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.095: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.096: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.096: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.097: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.098: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.098: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.098: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.098: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.098: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.099: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.100: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.100: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.101: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.101: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.101: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.101: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.102: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.102: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.103: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.103: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.104: Device reported enroll progress, reported 9 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.104: [goodixmoc] enroll entering state 5 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.104: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.104: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.105: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.105: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.106: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.107: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.107: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.107: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.107: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.108: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.108: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.108: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.109: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.110: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.110: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.110: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.110: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.111: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.111: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.111: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.112: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.112: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.113: Device reported enroll progress, reported 10 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.113: [goodixmoc] enroll entering state 5 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.113: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.113: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.113: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.114: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.114: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.115: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.116: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.116: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.116: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.116: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.117: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.117: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.118: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.118: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.118: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.118: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.118: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.119: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.119: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.120: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.120: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.121: Device reported enroll progress, reported 11 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.121: [goodixmoc] enroll entering state 5 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.121: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.121: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.121: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.122: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.122: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.123: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.123: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.123: [goodixmoc] enroll entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.123: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.124: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.124: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.124: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.125: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.126: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.126: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.126: [goodixmoc] enroll entering state 4 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.126: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.126: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.127: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.127: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.128: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.128: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.129: Device reported enroll progress, reported 12 of 12 have been completed 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.129: [goodixmoc] enroll entering state 6 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.129: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.129: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.129: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.130: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.130: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.131: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.132: [goodixmoc] enroll entering state 7 410s (process:2052): libfprint-goodixmoc-DEBUG: 05:08:50.132: user_id: FP1-00000000-0-00000000-nobody, user_id_len: 30, finger: 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.132: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.132: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.132: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.133: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.133: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.134: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.134: [goodixmoc] enroll entering state 8 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.134: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.135: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.135: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.135: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.136: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.136: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.137: [goodixmoc] enroll completed successfully 410s (process:2052): libfprint-goodixmoc-DEBUG: 05:08:50.137: Enrollment complete! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.137: Device reported enroll completion 410s (process:2052): libfprint-device-DEBUG: 05:08:50.137: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2052): libfprint-device-DEBUG: 05:08:50.137: Print for finger FP_FINGER_UNKNOWN enrolled 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.137: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-device-DEBUG: 05:08:50.137: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.137: Not updating temperature model, device can run continuously! 410s (process:2052): libfprint-goodixmoc-DEBUG: 05:08:50.137: 130989131537: ../libfprint/drivers/goodixmoc/goodix.c:1556 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.137: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.138: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.138: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.139: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.140: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-goodixmoc-DEBUG: 05:08:50.140: Query complete! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.140: Device reported listing completion 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.140: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-device-DEBUG: 05:08:50.140: Completing action FPI_DEVICE_ACTION_LIST in idle! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.140: Not updating temperature model, device can run continuously! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.140: Not updating temperature model, device can run continuously! 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.140: [goodixmoc] verify entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.140: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.141: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.142: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.142: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.143: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.143: [goodixmoc] verify entering state 1 410s (process:2052): libfprint-device-DEBUG: 05:08:50.143: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.143: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.144: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.144: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.144: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.145: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.146: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.146: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.146: [goodixmoc] verify entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.146: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.147: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.147: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.147: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.148: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.149: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-DEBUG: 05:08:50.149: match, score: 28, study: 0 410s (process:2052): libfprint-device-DEBUG: 05:08:50.149: Device reported verify result 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.149: [goodixmoc] verify entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.149: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.150: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.150: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.150: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.151: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.152: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.152: [goodixmoc] verify completed successfully 410s (process:2052): libfprint-goodixmoc-DEBUG: 05:08:50.152: Verify complete! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.152: Device reported verify completion 410s (process:2052): libfprint-device-DEBUG: 05:08:50.152: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.152: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-device-DEBUG: 05:08:50.152: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.152: Not updating temperature model, device can run continuously! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.153: Not updating temperature model, device can run continuously! 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.153: [goodixmoc] verify entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.153: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.154: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.154: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.155: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.155: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.156: [goodixmoc] verify entering state 1 410s (process:2052): libfprint-device-DEBUG: 05:08:50.156: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.156: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.156: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.157: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.157: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.158: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.158: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-device-DEBUG: 05:08:50.159: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.159: [goodixmoc] verify entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.159: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.159: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.159: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.160: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.160: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.161: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-DEBUG: 05:08:50.161: match, score: 35, study: 0 410s (process:2052): libfprint-device-DEBUG: 05:08:50.162: Device reported identify result 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.162: [goodixmoc] verify entering state 3 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.162: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.162: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.162: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.163: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.163: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.164: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.164: [goodixmoc] verify completed successfully 410s (process:2052): libfprint-goodixmoc-DEBUG: 05:08:50.164: Verify complete! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.164: Device reported identify completion 410s (process:2052): libfprint-device-DEBUG: 05:08:50.164: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.164: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-device-DEBUG: 05:08:50.164: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.164: Not updating temperature model, device can run continuously! 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.165: [goodixmoc] FP_CMD_NUM_STATES entering state 0 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.166: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.166: [goodixmoc] FP_CMD_NUM_STATES entering state 1 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.167: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.167: [goodixmoc] FP_CMD_NUM_STATES entering state 2 410s (process:2052): libfprint-goodixmoc-DEBUG: 05:08:50.168: Successfully deleted enrolled user 410s (process:2052): libfprint-device-DEBUG: 05:08:50.168: Device reported deletion completion 410s (process:2052): libfprint-SSM-DEBUG: 05:08:50.168: [goodixmoc] FP_CMD_NUM_STATES completed successfully 410s (process:2052): libfprint-device-DEBUG: 05:08:50.168: Completing action FPI_DEVICE_ACTION_DELETE in idle! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.168: Not updating temperature model, device can run continuously! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.168: Device reported close completion 410s (process:2052): libfprint-device-DEBUG: 05:08:50.168: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s (process:2052): libfprint-device-DEBUG: 05:08:50.168: Not updating temperature model, device can run continuously! 410s enrolling 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 1, None, None, None) 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 2, None, None, None) 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 3, None, None, None) 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 4, None, None, None) 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 5, None, None, None) 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 6, None, None, None) 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 7, None, None, None) 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 8, None, None, None) 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 9, None, None, None) 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 10, None, None, None) 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 11, None, None, None) 410s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xef77f628 (FpiDeviceGoodixMoc at 0x10d2e10)>, 12, None, None, None) 410s enroll done 410s listing 410s listing done 410s verifying 410s verify done 410s async identifying 410s indentification_done: 410s deleting 410s delete done 410s ** (umockdev-run:2048): DEBUG: 05:08:50.192: umockdev.vala:154: Removing test bed /tmp/umockdev.DGK512 410s (umockdev-run:2048): GLib-DEBUG: 05:08:50.200: unsetenv() is not thread-safe and should not be used after threads are created 410s PASS: libfprint-2/driver-goodixmoc.test 410s Running test: libfprint-2/virtual-image.test 410s (process:2058): libfprint-context-DEBUG: 05:08:50.337: Initializing FpContext (libfprint version 1.94.9+tod1) 410s (process:2058): libfprint-tod-DEBUG: 05:08:50.337: 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:2058): libfprint-context-DEBUG: 05:08:50.340: No driver found for USB device 1D6B:0003 410s (process:2058): libfprint-context-DEBUG: 05:08:50.340: No driver found for USB device 0627:0001 410s (process:2058): libfprint-context-DEBUG: 05:08:50.340: No driver found for USB device 1D6B:0002 410s (process:2058): libfprint-context-DEBUG: 05:08:50.340: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-dfjf960s/virtual-image.socket 410s (process:2058): libfprint-context-DEBUG: 05:08:50.340: created 410s (process:2058): libfprint-device-DEBUG: 05:08:50.341: Device reported probe completion 410s (process:2058): libfprint-device-DEBUG: 05:08:50.341: Completing action FPI_DEVICE_ACTION_PROBE in idle! 410s (process:2058): libfprint-device-DEBUG: 05:08:50.341: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s test_capture_prevents_close (__main__.VirtualImage.test_capture_prevents_close) ... (process:2058): libfprint-virtual_image-DEBUG: 05:08:50.348: 130989342342: ../libfprint/drivers/virtual-image.c:216 410s (process:2058): libfprint-virtual_device_connection-DEBUG: 05:08:50.348: 130989342458: ../libfprint/drivers/virtual-device-listener.c:153 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.449: Image device open completed 410s (process:2058): libfprint-device-DEBUG: 05:08:50.449: Device reported open completion 410s (process:2058): libfprint-device-DEBUG: 05:08:50.449: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s (process:2058): libfprint-device-DEBUG: 05:08:50.449: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s (process:2058): libfprint-device-DEBUG: 05:08:50.450: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.450: Activating image device 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.450: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.450: Image device activation completed 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.450: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.450: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 410s (process:2058): libfprint-device-DEBUG: 05:08:50.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2058): libfprint-virtual_device_connection-DEBUG: 05:08:50.450: Got a new connection! 410s (process:2058): libfprint-device-DEBUG: 05:08:50.451: Idle cancelling on ongoing operation! 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.451: Deactivating image device 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.451: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.451: Image device deactivation completed 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.451: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 410s (process:2058): libfprint-device-DEBUG: 05:08:50.451: Device reported generic error (Operation was cancelled) during action; action was: FPI_DEVICE_ACTION_CAPTURE 410s (process:2058): libfprint-device-DEBUG: 05:08:50.451: Device reported capture completion 410s (process:2058): libfprint-device-DEBUG: 05:08:50.451: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2058): libfprint-device-DEBUG: 05:08:50.451: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 410s (process:2058): libfprint-device-DEBUG: 05:08:50.451: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s (process:2058): libfprint-virtual_image-DEBUG: 05:08:50.452: 130989445922: ../libfprint/drivers/virtual-image.c:244 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.552: Image device close completed 410s (process:2058): libfprint-device-DEBUG: 05:08:50.552: Device reported close completion 410s (process:2058): libfprint-device-DEBUG: 05:08:50.552: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 410s (process:2058): libfprint-device-DEBUG: 05:08:50.552: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s Capture operation finished 410s Capture cancelled as expected 410s ok 410s test_enroll_verify (__main__.VirtualImage.test_enroll_verify) ... (process:2058): libfprint-virtual_image-DEBUG: 05:08:50.553: 130989546734: ../libfprint/drivers/virtual-image.c:216 410s (process:2058): libfprint-virtual_device_connection-DEBUG: 05:08:50.553: 130989546757: ../libfprint/drivers/virtual-device-listener.c:153 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.653: Image device open completed 410s (process:2058): libfprint-device-DEBUG: 05:08:50.653: Device reported open completion 410s (process:2058): libfprint-device-DEBUG: 05:08:50.653: Completing action FPI_DEVICE_ACTION_OPEN in idle! 410s (process:2058): libfprint-device-DEBUG: 05:08:50.653: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s (process:2058): libfprint-device-DEBUG: 05:08:50.655: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.655: Activating image device 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.655: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.655: Image device activation completed 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.655: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.655: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 410s (process:2058): libfprint-device-DEBUG: 05:08:50.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2058): libfprint-virtual_device_connection-DEBUG: 05:08:50.655: Got a new connection! 410s (process:2058): libfprint-virtual_image-DEBUG: 05:08:50.655: image data: 0x11728f0 410s (process:2058): libfprint-device-DEBUG: 05:08:50.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.655: Image device reported finger status: on 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.655: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.655: Image device captured an image 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.657: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 410s (process:2058): libfprint-device-DEBUG: 05:08:50.657: Device reported finger status change: FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-device-DEBUG: 05:08:50.657: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.657: Image device reported finger status: off 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.657: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 410s (process:2058): libfprint-image-DEBUG: 05:08:50.685: Minutiae scan completed in 0.028060 secs 410s (process:2058): libfprint-device-DEBUG: 05:08:50.685: Device reported enroll progress, reported 1 of 5 have been completed 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.685: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 410s (process:2058): libfprint-device-DEBUG: 05:08:50.685: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2058): libfprint-device-DEBUG: 05:08:50.685: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.685: Image device reported finger status: on 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.686: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 410s (process:2058): libfprint-virtual_image-DEBUG: 05:08:50.686: image data: 0x1163608 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.686: Image device captured an image 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.686: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 410s (process:2058): libfprint-device-DEBUG: 05:08:50.686: Device reported finger status change: FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-image-DEBUG: 05:08:50.714: Minutiae scan completed in 0.027794 secs 410s (process:2058): libfprint-device-DEBUG: 05:08:50.714: Device reported enroll progress, reported 2 of 5 have been completed 410s (process:2058): libfprint-device-DEBUG: 05:08:50.714: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.714: Image device reported finger status: off 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.714: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.714: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 410s (process:2058): libfprint-device-DEBUG: 05:08:50.714: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2058): libfprint-virtual_image-DEBUG: 05:08:50.714: image data: 0x1163608 410s (process:2058): libfprint-device-DEBUG: 05:08:50.715: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.715: Image device reported finger status: on 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.715: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.715: Image device captured an image 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.715: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 410s (process:2058): libfprint-device-DEBUG: 05:08:50.715: Device reported finger status change: FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-device-DEBUG: 05:08:50.715: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.715: Image device reported finger status: off 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.715: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 410s (process:2058): libfprint-image-DEBUG: 05:08:50.742: Minutiae scan completed in 0.027787 secs 410s (process:2058): libfprint-device-DEBUG: 05:08:50.743: Device reported enroll progress, reported 3 of 5 have been completed 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.743: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 410s (process:2058): libfprint-device-DEBUG: 05:08:50.743: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2058): libfprint-virtual_image-DEBUG: 05:08:50.743: image data: 0x1163608 410s (process:2058): libfprint-device-DEBUG: 05:08:50.743: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.743: Image device reported finger status: on 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.743: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.743: Image device captured an image 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.743: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 410s (process:2058): libfprint-device-DEBUG: 05:08:50.743: Device reported finger status change: FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-device-DEBUG: 05:08:50.743: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.743: Image device reported finger status: off 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.743: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 410s (process:2058): libfprint-image-DEBUG: 05:08:50.771: Minutiae scan completed in 0.027600 secs 410s (process:2058): libfprint-device-DEBUG: 05:08:50.771: Device reported enroll progress, reported 4 of 5 have been completed 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.771: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 410s (process:2058): libfprint-device-DEBUG: 05:08:50.771: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2058): libfprint-virtual_image-DEBUG: 05:08:50.772: image data: 0x1163608 410s (process:2058): libfprint-device-DEBUG: 05:08:50.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.772: Image device reported finger status: on 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.772: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.772: Image device captured an image 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.772: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 410s (process:2058): libfprint-device-DEBUG: 05:08:50.772: Device reported finger status change: FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-device-DEBUG: 05:08:50.772: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.772: Image device reported finger status: off 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.772: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 410s (process:2058): libfprint-device-DEBUG: 05:08:50.790: Updated temperature model after 0.14 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 410s (process:2058): libfprint-image-DEBUG: 05:08:50.799: Minutiae scan completed in 0.026609 secs 410s (process:2058): libfprint-device-DEBUG: 05:08:50.799: Device reported enroll progress, reported 5 of 5 have been completed 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.799: Deactivating image device 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.799: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.799: Image device deactivation completed 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.799: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 410s (process:2058): libfprint-device-DEBUG: 05:08:50.799: Device reported enroll completion 410s (process:2058): libfprint-device-DEBUG: 05:08:50.799: Print for finger FP_FINGER_LEFT_THUMB enrolled 410s (process:2058): libfprint-device-DEBUG: 05:08:50.799: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 410s (process:2058): libfprint-device-DEBUG: 05:08:50.799: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 410s (process:2058): libfprint-device-DEBUG: 05:08:50.800: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Activating image device 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device activation completed 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 410s (process:2058): libfprint-device-DEBUG: 05:08:50.800: Device reported finger status change: FP_FINGER_STATUS_NEEDED 410s (process:2058): libfprint-virtual_image-DEBUG: 05:08:50.800: image data: 0x1163608 410s (process:2058): libfprint-device-DEBUG: 05:08:50.800: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device reported finger status: on 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device captured an image 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 410s (process:2058): libfprint-device-DEBUG: 05:08:50.800: Device reported finger status change: FP_FINGER_STATUS_PRESENT 410s (process:2058): libfprint-device-DEBUG: 05:08:50.800: Device reported finger status change: FP_FINGER_STATUS_NONE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device reported finger status: off 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Deactivating image device 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device deactivation completed 410s (process:2058): libfprint-image_device-DEBUG: 05:08:50.800: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 410s (process:2058): libfprint-image-DEBUG: 05:08:50.828: Minutiae scan completed in 0.028067 secs 412s (process:2058): libfprint-print-DEBUG: 05:08:51.989: score 1093/40 412s (process:2058): libfprint-device-DEBUG: 05:08:51.989: Device reported verify result 412s (process:2058): libfprint-device-DEBUG: 05:08:51.989: Device reported verify completion 412s (process:2058): libfprint-device-DEBUG: 05:08:51.989: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 412s (process:2058): libfprint-device-DEBUG: 05:08:51.989: Updated temperature model after 1.19 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 412s (process:2058): libfprint-device-DEBUG: 05:08:51.990: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Activating image device 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device activation completed 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 412s (process:2058): libfprint-device-DEBUG: 05:08:51.990: Device reported finger status change: FP_FINGER_STATUS_NEEDED 412s (process:2058): libfprint-virtual_image-DEBUG: 05:08:51.990: image data: 0x11cbd88 412s (process:2058): libfprint-device-DEBUG: 05:08:51.990: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device reported finger status: on 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device captured an image 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 412s (process:2058): libfprint-device-DEBUG: 05:08:51.990: Device reported finger status change: FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-device-DEBUG: 05:08:51.990: Device reported finger status change: FP_FINGER_STATUS_NONE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device reported finger status: off 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Deactivating image device 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device deactivation completed 412s (process:2058): libfprint-image_device-DEBUG: 05:08:51.990: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 412s (process:2058): libfprint-image-DEBUG: 05:08:52.016: Minutiae scan completed in 0.025222 secs 412s (process:2058): libfprint-print-DEBUG: 05:08:52.023: score 10/40 412s (process:2058): libfprint-print-DEBUG: 05:08:52.030: score 10/40 412s (process:2058): libfprint-print-DEBUG: 05:08:52.036: score 10/40 412s (process:2058): libfprint-print-DEBUG: 05:08:52.043: score 10/40 412s (process:2058): libfprint-print-DEBUG: 05:08:52.049: score 10/40 412s (process:2058): libfprint-device-DEBUG: 05:08:52.049: Device reported verify result 412s (process:2058): libfprint-device-DEBUG: 05:08:52.049: Device reported verify completion 412s (process:2058): libfprint-device-DEBUG: 05:08:52.049: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 412s (process:2058): libfprint-device-DEBUG: 05:08:52.049: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 412s (process:2058): libfprint-device-DEBUG: 05:08:52.049: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.050: Activating image device 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.050: Image device activation completed 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 412s (process:2058): libfprint-device-DEBUG: 05:08:52.050: Device reported finger status change: FP_FINGER_STATUS_NEEDED 412s (process:2058): libfprint-virtual_image-DEBUG: 05:08:52.050: image data: 0x11dad90 412s (process:2058): libfprint-device-DEBUG: 05:08:52.050: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.050: Image device reported finger status: on 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.050: Image device captured an image 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 412s (process:2058): libfprint-device-DEBUG: 05:08:52.050: Device reported finger status change: FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-device-DEBUG: 05:08:52.050: Device reported finger status change: FP_FINGER_STATUS_NONE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.050: Image device reported finger status: off 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.050: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 412s (process:2058): libfprint-image-DEBUG: 05:08:52.075: Minutiae scan completed in 0.024784 secs 412s (process:2058): libfprint-device-DEBUG: 05:08:52.075: Device reported enroll progress, reported 1 of 5 have been completed 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.075: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 412s (process:2058): libfprint-device-DEBUG: 05:08:52.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED 412s (process:2058): libfprint-device-DEBUG: 05:08:52.076: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.076: Image device reported finger status: on 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 412s (process:2058): libfprint-virtual_image-DEBUG: 05:08:52.076: image data: 0x11dad90 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.076: Image device captured an image 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 412s (process:2058): libfprint-device-DEBUG: 05:08:52.076: Device reported finger status change: FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-image-DEBUG: 05:08:52.101: Minutiae scan completed in 0.024671 secs 412s (process:2058): libfprint-device-DEBUG: 05:08:52.101: Device reported enroll progress, reported 2 of 5 have been completed 412s (process:2058): libfprint-device-DEBUG: 05:08:52.101: Device reported finger status change: FP_FINGER_STATUS_NONE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.101: Image device reported finger status: off 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.101: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.101: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 412s (process:2058): libfprint-device-DEBUG: 05:08:52.101: Device reported finger status change: FP_FINGER_STATUS_NEEDED 412s (process:2058): libfprint-virtual_image-DEBUG: 05:08:52.101: image data: 0x11dad90 412s (process:2058): libfprint-device-DEBUG: 05:08:52.102: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.102: Image device reported finger status: on 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.102: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.102: Image device captured an image 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.102: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 412s (process:2058): libfprint-device-DEBUG: 05:08:52.102: Device reported finger status change: FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-device-DEBUG: 05:08:52.102: Device reported finger status change: FP_FINGER_STATUS_NONE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.102: Image device reported finger status: off 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.102: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 412s (process:2058): libfprint-image-DEBUG: 05:08:52.126: Minutiae scan completed in 0.024725 secs 412s (process:2058): libfprint-device-DEBUG: 05:08:52.127: Device reported enroll progress, reported 3 of 5 have been completed 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.127: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 412s (process:2058): libfprint-device-DEBUG: 05:08:52.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED 412s (process:2058): libfprint-virtual_image-DEBUG: 05:08:52.127: image data: 0x11dad90 412s (process:2058): libfprint-device-DEBUG: 05:08:52.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.127: Image device reported finger status: on 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.127: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.127: Image device captured an image 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.127: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 412s (process:2058): libfprint-device-DEBUG: 05:08:52.127: Device reported finger status change: FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-device-DEBUG: 05:08:52.127: Device reported finger status change: FP_FINGER_STATUS_NONE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.127: Image device reported finger status: off 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.127: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 412s (process:2058): libfprint-image-DEBUG: 05:08:52.152: Minutiae scan completed in 0.024651 secs 412s (process:2058): libfprint-device-DEBUG: 05:08:52.152: Device reported enroll progress, reported 4 of 5 have been completed 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.152: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 412s (process:2058): libfprint-device-DEBUG: 05:08:52.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED 412s (process:2058): libfprint-virtual_image-DEBUG: 05:08:52.153: image data: 0x11dad90 412s (process:2058): libfprint-device-DEBUG: 05:08:52.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.153: Image device reported finger status: on 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.153: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.153: Image device captured an image 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.153: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 412s (process:2058): libfprint-device-DEBUG: 05:08:52.153: Device reported finger status change: FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-device-DEBUG: 05:08:52.153: Device reported finger status change: FP_FINGER_STATUS_NONE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.153: Image device reported finger status: off 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.153: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 412s (process:2058): libfprint-image-DEBUG: 05:08:52.178: Minutiae scan completed in 0.025224 secs 412s (process:2058): libfprint-device-DEBUG: 05:08:52.178: Device reported enroll progress, reported 5 of 5 have been completed 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.178: Deactivating image device 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.178: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.178: Image device deactivation completed 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.178: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 412s (process:2058): libfprint-device-DEBUG: 05:08:52.178: Device reported enroll completion 412s (process:2058): libfprint-device-DEBUG: 05:08:52.178: Print for finger FP_FINGER_LEFT_THUMB enrolled 412s (process:2058): libfprint-device-DEBUG: 05:08:52.178: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 412s (process:2058): libfprint-device-DEBUG: 05:08:52.178: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 412s (process:2058): libfprint-device-DEBUG: 05:08:52.179: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Activating image device 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device activation completed 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 412s (process:2058): libfprint-device-DEBUG: 05:08:52.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED 412s (process:2058): libfprint-virtual_image-DEBUG: 05:08:52.179: image data: 0x1163608 412s (process:2058): libfprint-device-DEBUG: 05:08:52.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device reported finger status: on 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device captured an image 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 412s (process:2058): libfprint-device-DEBUG: 05:08:52.179: Device reported finger status change: FP_FINGER_STATUS_PRESENT 412s (process:2058): libfprint-device-DEBUG: 05:08:52.179: Device reported finger status change: FP_FINGER_STATUS_NONE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device reported finger status: off 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Deactivating image device 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device deactivation completed 412s (process:2058): libfprint-image_device-DEBUG: 05:08:52.179: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 412s (process:2058): libfprint-image-DEBUG: 05:08:52.208: Minutiae scan completed in 0.028710 secs 412s Executing: libfprint-2/virtual-image.test 413s (process:2058): libfprint-print-DEBUG: 05:08:53.353: score 1093/40 413s (process:2058): libfprint-device-DEBUG: 05:08:53.353: Device reported verify result 413s (process:2058): libfprint-device-DEBUG: 05:08:53.353: Device reported verify completion 413s (process:2058): libfprint-device-DEBUG: 05:08:53.353: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 413s (process:2058): libfprint-device-DEBUG: 05:08:53.353: Updated temperature model after 1.17 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 413s (process:2058): libfprint-device-DEBUG: 05:08:53.354: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Activating image device 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device activation completed 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 413s (process:2058): libfprint-device-DEBUG: 05:08:53.354: Device reported finger status change: FP_FINGER_STATUS_NEEDED 413s (process:2058): libfprint-virtual_image-DEBUG: 05:08:53.354: image data: 0x11cbd88 413s (process:2058): libfprint-device-DEBUG: 05:08:53.354: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device reported finger status: on 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device captured an image 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 413s (process:2058): libfprint-device-DEBUG: 05:08:53.354: Device reported finger status change: FP_FINGER_STATUS_PRESENT 413s (process:2058): libfprint-device-DEBUG: 05:08:53.354: Device reported finger status change: FP_FINGER_STATUS_NONE 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device reported finger status: off 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Deactivating image device 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device deactivation completed 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.354: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 413s (process:2058): libfprint-image-DEBUG: 05:08:53.379: Minutiae scan completed in 0.024861 secs 413s (process:2058): libfprint-print-DEBUG: 05:08:53.386: score 10/40 413s (process:2058): libfprint-print-DEBUG: 05:08:53.393: score 10/40 413s (process:2058): libfprint-print-DEBUG: 05:08:53.399: score 10/40 413s (process:2058): libfprint-print-DEBUG: 05:08:53.406: score 10/40 413s (process:2058): libfprint-print-DEBUG: 05:08:53.412: score 10/40 413s (process:2058): libfprint-print-DEBUG: 05:08:53.644: score 855/40 413s (process:2058): libfprint-device-DEBUG: 05:08:53.644: Device reported verify result 413s (process:2058): libfprint-device-DEBUG: 05:08:53.644: Device reported verify completion 413s (process:2058): libfprint-device-DEBUG: 05:08:53.644: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 413s (process:2058): libfprint-device-DEBUG: 05:08:53.644: Updated temperature model after 0.29 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 413s (process:2058): libfprint-device-DEBUG: 05:08:53.644: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.644: Activating image device 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.644: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.644: Image device activation completed 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.644: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.644: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 413s (process:2058): libfprint-device-DEBUG: 05:08:53.644: Device reported finger status change: FP_FINGER_STATUS_NEEDED 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Device reported verify result 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Deactivating image device 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Image device deactivation completed 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Device reported verify completion 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Device reported finger status change: FP_FINGER_STATUS_NONE 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Activating image device 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Image device activation completed 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Device reported finger status change: FP_FINGER_STATUS_NEEDED 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Deactivating image device 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Image device deactivation completed 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.645: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_VERIFY 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Device reported verify completion 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Device reported finger status change: FP_FINGER_STATUS_NONE 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 413s (process:2058): libfprint-device-DEBUG: 05:08:53.645: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 413s (process:2058): libfprint-virtual_image-DEBUG: 05:08:53.645: 130992639498: ../libfprint/drivers/virtual-image.c:244 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.745: Image device close completed 413s (process:2058): libfprint-device-DEBUG: 05:08:53.745: Device reported close completion 413s (process:2058): libfprint-device-DEBUG: 05:08:53.745: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 413s (process:2058): libfprint-device-DEBUG: 05:08:53.745: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 413s Print was processed, continuing 413s Print was processed, continuing 413s Print was processed, continuing 413s Print was processed, continuing 413s Print was processed, continuing 413s Enroll done 413s Print was processed, continuing 413s Print was processed, continuing 413s Print was processed, continuing 413s Print was processed, continuing 413s Print was processed, continuing 413s Enroll done 413s fp - device - error - quark: An unspecified error occurred! (0) 413s ok 413s test_features (__main__.VirtualImage.test_features) ... (process:2058): libfprint-virtual_image-DEBUG: 05:08:53.746: 130992739916: ../libfprint/drivers/virtual-image.c:216 413s (process:2058): libfprint-virtual_device_connection-DEBUG: 05:08:53.746: 130992739938: ../libfprint/drivers/virtual-device-listener.c:153 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.846: Image device open completed 413s (process:2058): libfprint-device-DEBUG: 05:08:53.846: Device reported open completion 413s (process:2058): libfprint-device-DEBUG: 05:08:53.846: Completing action FPI_DEVICE_ACTION_OPEN in idle! 413s (process:2058): libfprint-device-DEBUG: 05:08:53.846: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 413s (process:2058): libfprint-virtual_image-DEBUG: 05:08:53.846: 130992840344: ../libfprint/drivers/virtual-image.c:244 413s (process:2058): libfprint-image_device-DEBUG: 05:08:53.946: Image device close completed 413s (process:2058): libfprint-device-DEBUG: 05:08:53.946: Device reported close completion 413s (process:2058): libfprint-device-DEBUG: 05:08:53.946: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 413s (process:2058): libfprint-device-DEBUG: 05:08:53.946: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 413s ok 413s test_identify (__main__.VirtualImage.test_identify) ... (process:2058): libfprint-virtual_image-DEBUG: 05:08:53.946: 130992940456: ../libfprint/drivers/virtual-image.c:216 413s (process:2058): libfprint-virtual_device_connection-DEBUG: 05:08:53.946: 130992940468: ../libfprint/drivers/virtual-device-listener.c:153 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.046: Image device open completed 414s (process:2058): libfprint-device-DEBUG: 05:08:54.046: Device reported open completion 414s (process:2058): libfprint-device-DEBUG: 05:08:54.046: Completing action FPI_DEVICE_ACTION_OPEN in idle! 414s (process:2058): libfprint-device-DEBUG: 05:08:54.046: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 414s (process:2058): libfprint-device-DEBUG: 05:08:54.047: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.047: Activating image device 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.047: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.047: Image device activation completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.047: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.047: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.047: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-virtual_device_connection-DEBUG: 05:08:54.047: Got a new connection! 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.047: image data: 0x1163608 414s (process:2058): libfprint-device-DEBUG: 05:08:54.047: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.047: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.047: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.047: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.047: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.047: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-device-DEBUG: 05:08:54.047: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.047: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.047: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image-DEBUG: 05:08:54.075: Minutiae scan completed in 0.028050 secs 414s (process:2058): libfprint-device-DEBUG: 05:08:54.076: Device reported enroll progress, reported 1 of 5 have been completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.076: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-device-DEBUG: 05:08:54.076: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.076: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.076: image data: 0x1163608 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.076: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.076: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image-DEBUG: 05:08:54.104: Minutiae scan completed in 0.027658 secs 414s (process:2058): libfprint-device-DEBUG: 05:08:54.104: Device reported enroll progress, reported 2 of 5 have been completed 414s (process:2058): libfprint-device-DEBUG: 05:08:54.104: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.104: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.104: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.104: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.105: image data: 0x1163608 414s (process:2058): libfprint-device-DEBUG: 05:08:54.105: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.105: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.105: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.105: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.105: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.105: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-device-DEBUG: 05:08:54.105: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.105: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.105: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image-DEBUG: 05:08:54.132: Minutiae scan completed in 0.027397 secs 414s (process:2058): libfprint-device-DEBUG: 05:08:54.132: Device reported enroll progress, reported 3 of 5 have been completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.132: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.132: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.132: image data: 0x1163608 414s (process:2058): libfprint-device-DEBUG: 05:08:54.133: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.133: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.133: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.133: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.133: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.133: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-device-DEBUG: 05:08:54.133: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.133: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.133: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image-DEBUG: 05:08:54.161: Minutiae scan completed in 0.027978 secs 414s (process:2058): libfprint-device-DEBUG: 05:08:54.161: Device reported enroll progress, reported 4 of 5 have been completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.161: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.161: image data: 0x1163608 414s (process:2058): libfprint-device-DEBUG: 05:08:54.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.161: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.161: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.161: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.161: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.161: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-device-DEBUG: 05:08:54.161: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.161: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.161: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image-DEBUG: 05:08:54.188: Minutiae scan completed in 0.026795 secs 414s (process:2058): libfprint-device-DEBUG: 05:08:54.189: Device reported enroll progress, reported 5 of 5 have been completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Deactivating image device 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device deactivation completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 414s (process:2058): libfprint-device-DEBUG: 05:08:54.189: Device reported enroll completion 414s (process:2058): libfprint-device-DEBUG: 05:08:54.189: Print for finger FP_FINGER_LEFT_THUMB enrolled 414s (process:2058): libfprint-device-DEBUG: 05:08:54.189: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 414s (process:2058): libfprint-device-DEBUG: 05:08:54.189: Updated temperature model after 0.14 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 414s (process:2058): libfprint-device-DEBUG: 05:08:54.189: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Activating image device 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device activation completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.189: image data: 0x11cbd88 414s (process:2058): libfprint-device-DEBUG: 05:08:54.189: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.189: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-device-DEBUG: 05:08:54.189: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.189: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image-DEBUG: 05:08:54.215: Minutiae scan completed in 0.025304 secs 414s (process:2058): libfprint-device-DEBUG: 05:08:54.215: Device reported enroll progress, reported 1 of 5 have been completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.215: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.215: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-device-DEBUG: 05:08:54.215: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.215: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.215: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.216: image data: 0x11cbd88 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.216: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.216: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.216: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image-DEBUG: 05:08:54.240: Minutiae scan completed in 0.024429 secs 414s (process:2058): libfprint-device-DEBUG: 05:08:54.240: Device reported enroll progress, reported 2 of 5 have been completed 414s (process:2058): libfprint-device-DEBUG: 05:08:54.241: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.241: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.241: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.241: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.241: image data: 0x11cbd88 414s (process:2058): libfprint-device-DEBUG: 05:08:54.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.241: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.241: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.241: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.241: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.241: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-device-DEBUG: 05:08:54.241: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.241: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.241: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image-DEBUG: 05:08:54.266: Minutiae scan completed in 0.024670 secs 414s (process:2058): libfprint-device-DEBUG: 05:08:54.266: Device reported enroll progress, reported 3 of 5 have been completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.266: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.266: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.266: image data: 0x11cbd88 414s (process:2058): libfprint-device-DEBUG: 05:08:54.266: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.266: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.266: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.266: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.266: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.266: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-device-DEBUG: 05:08:54.266: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.266: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.266: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image-DEBUG: 05:08:54.292: Minutiae scan completed in 0.025214 secs 414s (process:2058): libfprint-device-DEBUG: 05:08:54.292: Device reported enroll progress, reported 4 of 5 have been completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.292: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.292: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.292: image data: 0x11cbd88 414s (process:2058): libfprint-device-DEBUG: 05:08:54.292: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.292: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.292: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.292: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.292: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.292: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-device-DEBUG: 05:08:54.292: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.292: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.292: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image-DEBUG: 05:08:54.317: Minutiae scan completed in 0.024835 secs 414s (process:2058): libfprint-device-DEBUG: 05:08:54.317: Device reported enroll progress, reported 5 of 5 have been completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.317: Deactivating image device 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.317: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.317: Image device deactivation completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.317: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 414s (process:2058): libfprint-device-DEBUG: 05:08:54.317: Device reported enroll completion 414s (process:2058): libfprint-device-DEBUG: 05:08:54.317: Print for finger FP_FINGER_LEFT_THUMB enrolled 414s (process:2058): libfprint-device-DEBUG: 05:08:54.318: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 414s (process:2058): libfprint-device-DEBUG: 05:08:54.318: Updated temperature model after 0.13 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 414s (process:2058): libfprint-device-DEBUG: 05:08:54.318: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Activating image device 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device activation completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.318: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.318: image data: 0x11cbd88 414s (process:2058): libfprint-device-DEBUG: 05:08:54.318: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.318: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-device-DEBUG: 05:08:54.318: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Deactivating image device 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device deactivation completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.318: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 414s (process:2058): libfprint-image-DEBUG: 05:08:54.343: Minutiae scan completed in 0.024807 secs 414s (process:2058): libfprint-print-DEBUG: 05:08:54.351: score 10/40 414s (process:2058): libfprint-print-DEBUG: 05:08:54.357: score 10/40 414s (process:2058): libfprint-print-DEBUG: 05:08:54.363: score 10/40 414s (process:2058): libfprint-print-DEBUG: 05:08:54.370: score 10/40 414s (process:2058): libfprint-print-DEBUG: 05:08:54.376: score 10/40 414s (process:2058): libfprint-print-DEBUG: 05:08:54.608: score 855/40 414s (process:2058): libfprint-device-DEBUG: 05:08:54.608: Device reported identify result 414s (process:2058): libfprint-device-DEBUG: 05:08:54.608: Device reported identify completion 414s (process:2058): libfprint-device-DEBUG: 05:08:54.608: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 414s (process:2058): libfprint-device-DEBUG: 05:08:54.608: Updated temperature model after 0.29 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 414s (process:2058): libfprint-device-DEBUG: 05:08:54.608: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.608: Activating image device 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device activation completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 414s (process:2058): libfprint-device-DEBUG: 05:08:54.609: Device reported finger status change: FP_FINGER_STATUS_NEEDED 414s (process:2058): libfprint-virtual_image-DEBUG: 05:08:54.609: image data: 0x1163600 414s (process:2058): libfprint-device-DEBUG: 05:08:54.609: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device reported finger status: on 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device captured an image 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 414s (process:2058): libfprint-device-DEBUG: 05:08:54.609: Device reported finger status change: FP_FINGER_STATUS_PRESENT 414s (process:2058): libfprint-device-DEBUG: 05:08:54.609: Device reported finger status change: FP_FINGER_STATUS_NONE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device reported finger status: off 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Deactivating image device 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device deactivation completed 414s (process:2058): libfprint-image_device-DEBUG: 05:08:54.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 414s (process:2058): libfprint-image-DEBUG: 05:08:54.637: Minutiae scan completed in 0.027577 secs 415s (process:2058): libfprint-print-DEBUG: 05:08:55.783: score 1093/40 415s (process:2058): libfprint-device-DEBUG: 05:08:55.783: Device reported identify result 415s (process:2058): libfprint-device-DEBUG: 05:08:55.783: Device reported identify completion 415s (process:2058): libfprint-device-DEBUG: 05:08:55.783: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 415s (process:2058): libfprint-device-DEBUG: 05:08:55.783: Updated temperature model after 1.17 seconds, ratio 0.28 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 415s (process:2058): libfprint-device-DEBUG: 05:08:55.783: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.783: Activating image device 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.783: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.783: Image device activation completed 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.783: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.783: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 415s (process:2058): libfprint-device-DEBUG: 05:08:55.783: Device reported finger status change: FP_FINGER_STATUS_NEEDED 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Device reported identify result 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Deactivating image device 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Image device deactivation completed 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Device reported identify completion 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Device reported finger status change: FP_FINGER_STATUS_NONE 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Activating image device 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Image device activation completed 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Device reported finger status change: FP_FINGER_STATUS_NEEDED 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Deactivating image device 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Image device deactivation completed 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.784: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Device reported identify completion 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Device reported finger status change: FP_FINGER_STATUS_NONE 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 415s (process:2058): libfprint-device-DEBUG: 05:08:55.784: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 415s (process:2058): libfprint-virtual_image-DEBUG: 05:08:55.784: 130994778476: ../libfprint/drivers/virtual-image.c:244 415s (process:2058): libfprint-image_device-DEBUG: 05:08:55.884: Image device close completed 415s (process:2058): libfprint-device-DEBUG: 05:08:55.884: Device reported close completion 415s (process:2058): libfprint-device-DEBUG: 05:08:55.884: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 415s (process:2058): libfprint-device-DEBUG: 05:08:55.884: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 415s Print was processed, continuing 415s Print was processed, continuing 415s Print was processed, continuing 415s Print was processed, continuing 415s Print was processed, continuing 415s Enroll done 415s Print was processed, continuing 415s Print was processed, continuing 415s Print was processed, continuing 415s Print was processed, continuing 415s Print was processed, continuing 415s Enroll done 415s Identify finished 415s Identify finished 415s Identify finished 415s fp - device - retry - quark: The swipe was too short, please try again. (1) 415s Identify finished 415s fp - device - error - quark: An unspecified error occurred! (0) 415s ok 415s test_verify_serialized (__main__.VirtualImage.test_verify_serialized) ... (process:2058): libfprint-virtual_image-DEBUG: 05:08:55.885: 130994878882: ../libfprint/drivers/virtual-image.c:216 415s (process:2058): libfprint-virtual_device_connection-DEBUG: 05:08:55.885: 130994878895: ../libfprint/drivers/virtual-device-listener.c:153 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.985: Image device open completed 416s (process:2058): libfprint-device-DEBUG: 05:08:55.985: Device reported open completion 416s (process:2058): libfprint-device-DEBUG: 05:08:55.985: Completing action FPI_DEVICE_ACTION_OPEN in idle! 416s (process:2058): libfprint-device-DEBUG: 05:08:55.985: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 416s (process:2058): libfprint-device-DEBUG: 05:08:55.985: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.985: Activating image device 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.985: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.985: Image device activation completed 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.985: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.985: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 416s (process:2058): libfprint-device-DEBUG: 05:08:55.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED 416s (process:2058): libfprint-virtual_device_connection-DEBUG: 05:08:55.986: Got a new connection! 416s (process:2058): libfprint-virtual_image-DEBUG: 05:08:55.986: image data: 0x1163600 416s (process:2058): libfprint-device-DEBUG: 05:08:55.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.986: Image device reported finger status: on 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.986: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.986: Image device captured an image 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.986: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 416s (process:2058): libfprint-device-DEBUG: 05:08:55.986: Device reported finger status change: FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-device-DEBUG: 05:08:55.986: Device reported finger status change: FP_FINGER_STATUS_NONE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.986: Image device reported finger status: off 416s (process:2058): libfprint-image_device-DEBUG: 05:08:55.986: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 416s (process:2058): libfprint-image-DEBUG: 05:08:56.013: Minutiae scan completed in 0.027472 secs 416s (process:2058): libfprint-device-DEBUG: 05:08:56.014: Device reported enroll progress, reported 1 of 5 have been completed 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.014: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 416s (process:2058): libfprint-device-DEBUG: 05:08:56.014: Device reported finger status change: FP_FINGER_STATUS_NEEDED 416s (process:2058): libfprint-device-DEBUG: 05:08:56.014: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.014: Image device reported finger status: on 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.014: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 416s (process:2058): libfprint-virtual_image-DEBUG: 05:08:56.014: image data: 0x1163600 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.014: Image device captured an image 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.014: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 416s (process:2058): libfprint-device-DEBUG: 05:08:56.014: Device reported finger status change: FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-image-DEBUG: 05:08:56.042: Minutiae scan completed in 0.027312 secs 416s (process:2058): libfprint-device-DEBUG: 05:08:56.042: Device reported enroll progress, reported 2 of 5 have been completed 416s (process:2058): libfprint-device-DEBUG: 05:08:56.042: Device reported finger status change: FP_FINGER_STATUS_NONE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.042: Image device reported finger status: off 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.042: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.042: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 416s (process:2058): libfprint-device-DEBUG: 05:08:56.042: Device reported finger status change: FP_FINGER_STATUS_NEEDED 416s (process:2058): libfprint-virtual_image-DEBUG: 05:08:56.042: image data: 0x1163600 416s (process:2058): libfprint-device-DEBUG: 05:08:56.043: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.043: Image device reported finger status: on 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.043: Image device captured an image 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 416s (process:2058): libfprint-device-DEBUG: 05:08:56.043: Device reported finger status change: FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-device-DEBUG: 05:08:56.043: Device reported finger status change: FP_FINGER_STATUS_NONE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.043: Image device reported finger status: off 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 416s (process:2058): libfprint-image-DEBUG: 05:08:56.070: Minutiae scan completed in 0.027471 secs 416s (process:2058): libfprint-device-DEBUG: 05:08:56.070: Device reported enroll progress, reported 3 of 5 have been completed 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.070: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 416s (process:2058): libfprint-device-DEBUG: 05:08:56.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED 416s (process:2058): libfprint-virtual_image-DEBUG: 05:08:56.071: image data: 0x1163600 416s (process:2058): libfprint-device-DEBUG: 05:08:56.071: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.071: Image device reported finger status: on 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.071: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.071: Image device captured an image 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.071: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 416s (process:2058): libfprint-device-DEBUG: 05:08:56.071: Device reported finger status change: FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-device-DEBUG: 05:08:56.071: Device reported finger status change: FP_FINGER_STATUS_NONE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.071: Image device reported finger status: off 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.071: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 416s (process:2058): libfprint-image-DEBUG: 05:08:56.098: Minutiae scan completed in 0.027181 secs 416s (process:2058): libfprint-device-DEBUG: 05:08:56.098: Device reported enroll progress, reported 4 of 5 have been completed 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.098: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 416s (process:2058): libfprint-device-DEBUG: 05:08:56.098: Device reported finger status change: FP_FINGER_STATUS_NEEDED 416s (process:2058): libfprint-virtual_image-DEBUG: 05:08:56.099: image data: 0x1163600 416s (process:2058): libfprint-device-DEBUG: 05:08:56.099: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.099: Image device reported finger status: on 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.099: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.099: Image device captured an image 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.099: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 416s (process:2058): libfprint-device-DEBUG: 05:08:56.099: Device reported finger status change: FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-device-DEBUG: 05:08:56.099: Device reported finger status change: FP_FINGER_STATUS_NONE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.099: Image device reported finger status: off 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.099: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 416s (process:2058): libfprint-image-DEBUG: 05:08:56.128: Minutiae scan completed in 0.029189 secs 416s (process:2058): libfprint-device-DEBUG: 05:08:56.128: Device reported enroll progress, reported 5 of 5 have been completed 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.128: Deactivating image device 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.128: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.128: Image device deactivation completed 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.128: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 416s (process:2058): libfprint-device-DEBUG: 05:08:56.128: Device reported enroll completion 416s (process:2058): libfprint-device-DEBUG: 05:08:56.128: Print for finger FP_FINGER_LEFT_THUMB enrolled 416s (process:2058): libfprint-device-DEBUG: 05:08:56.128: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 416s (process:2058): libfprint-device-DEBUG: 05:08:56.128: Updated temperature model after 0.14 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 416s (process:2058): libfprint-device-DEBUG: 05:08:56.129: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Activating image device 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device activation completed 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 416s (process:2058): libfprint-device-DEBUG: 05:08:56.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED 416s (process:2058): libfprint-virtual_image-DEBUG: 05:08:56.129: image data: 0x1163600 416s (process:2058): libfprint-device-DEBUG: 05:08:56.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device reported finger status: on 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device captured an image 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 416s (process:2058): libfprint-device-DEBUG: 05:08:56.129: Device reported finger status change: FP_FINGER_STATUS_PRESENT 416s (process:2058): libfprint-device-DEBUG: 05:08:56.129: Device reported finger status change: FP_FINGER_STATUS_NONE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device reported finger status: off 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Deactivating image device 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device deactivation completed 416s (process:2058): libfprint-image_device-DEBUG: 05:08:56.129: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 416s (process:2058): libfprint-image-DEBUG: 05:08:56.157: Minutiae scan completed in 0.027825 secs 417s (process:2058): libfprint-print-DEBUG: 05:08:57.304: score 1093/40 417s (process:2058): libfprint-device-DEBUG: 05:08:57.304: Device reported verify result 417s (process:2058): libfprint-device-DEBUG: 05:08:57.304: Device reported verify completion 417s (process:2058): libfprint-device-DEBUG: 05:08:57.304: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 417s (process:2058): libfprint-device-DEBUG: 05:08:57.304: Updated temperature model after 1.18 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 417s (process:2058): libfprint-device-DEBUG: 05:08:57.304: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.304: Activating image device 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.304: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.304: Image device activation completed 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.304: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.304: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 417s (process:2058): libfprint-device-DEBUG: 05:08:57.304: Device reported finger status change: FP_FINGER_STATUS_NEEDED 417s (process:2058): libfprint-virtual_image-DEBUG: 05:08:57.304: image data: 0x11cbd88 417s (process:2058): libfprint-device-DEBUG: 05:08:57.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.305: Image device reported finger status: on 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.305: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.305: Image device captured an image 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.305: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 417s (process:2058): libfprint-device-DEBUG: 05:08:57.305: Device reported finger status change: FP_FINGER_STATUS_PRESENT 417s (process:2058): libfprint-device-DEBUG: 05:08:57.305: Device reported finger status change: FP_FINGER_STATUS_NONE 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.305: Image device reported finger status: off 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.305: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.305: Deactivating image device 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.305: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.305: Image device deactivation completed 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.305: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 417s (process:2058): libfprint-image-DEBUG: 05:08:57.330: Minutiae scan completed in 0.025121 secs 417s (process:2058): libfprint-print-DEBUG: 05:08:57.337: score 10/40 417s (process:2058): libfprint-print-DEBUG: 05:08:57.344: score 10/40 417s (process:2058): libfprint-print-DEBUG: 05:08:57.350: score 10/40 417s (process:2058): libfprint-print-DEBUG: 05:08:57.356: score 10/40 417s (process:2058): libfprint-print-DEBUG: 05:08:57.363: score 10/40 417s (process:2058): libfprint-device-DEBUG: 05:08:57.363: Device reported verify result 417s (process:2058): libfprint-device-DEBUG: 05:08:57.363: Device reported verify completion 417s (process:2058): libfprint-device-DEBUG: 05:08:57.363: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 417s (process:2058): libfprint-device-DEBUG: 05:08:57.363: Updated temperature model after 0.06 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 417s (process:2058): libfprint-virtual_image-DEBUG: 05:08:57.363: 130996357507: ../libfprint/drivers/virtual-image.c:244 417s (process:2058): libfprint-image_device-DEBUG: 05:08:57.463: Image device close completed 417s (process:2058): libfprint-device-DEBUG: 05:08:57.463: Device reported close completion 417s (process:2058): libfprint-device-DEBUG: 05:08:57.463: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 417s (process:2058): libfprint-device-DEBUG: 05:08:57.463: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 417s Print was processed, continuing 417s Print was processed, continuing 417s Print was processed, continuing 417s Print was processed, continuing 417s Print was processed, continuing 417s Enroll done 417s ok 417s 417s ---------------------------------------------------------------------- 417s Ran 5 tests in 7.130s 417s 417s OK 417s PASS: libfprint-2/virtual-image.test 417s Running test: libfprint-2/driver-nb1010.test 417s ** (umockdev-run:2067): DEBUG: 05:08:57.550: umockdev.vala:127: Created udev test bed /tmp/umockdev.4OF112 417s ** (umockdev-run:2067): DEBUG: 05:08:57.551: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 417s ** (umockdev-run:2067): DEBUG: 05:08:57.556: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 (subsystem usb) 417s ** (umockdev-run:2067): DEBUG: 05:08:57.561: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4OF112/dev/bus/usb/001/003 417s ** (umockdev-run:2067): DEBUG: 05:08:57.561: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 417s ** (umockdev-run:2067): DEBUG: 05:08:57.567: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 (subsystem usb) 417s ** (umockdev-run:2067): DEBUG: 05:08:57.570: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.4OF112/dev/bus/usb/001/001 417s ** (umockdev-run:2067): DEBUG: 05:08:57.571: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0 417s ** (umockdev-run:2067): DEBUG: 05:08:57.574: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0 (subsystem pci) 417s ** (umockdev-run:2067): DEBUG: 05:08:57.577: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3 417s ** (umockdev-run:2067): DEBUG: 05:08:57.578: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3 (subsystem pci) 417s (umockdev-run:2067): GLib-GIO-DEBUG: 05:08:57.582: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 417s (process:2071): libfprint-context-DEBUG: 05:08:57.688: Initializing FpContext (libfprint version 1.94.9+tod1) 417s (process:2071): libfprint-tod-DEBUG: 05:08:57.688: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 417s (process:2071): libfprint-context-DEBUG: 05:08:57.691: No driver found for USB device 1D6B:0002 417s (process:2071): libfprint-device-DEBUG: 05:08:57.691: Device reported probe completion 417s (process:2071): libfprint-device-DEBUG: 05:08:57.691: Completing action FPI_DEVICE_ACTION_PROBE in idle! 417s (process:2071): libfprint-device-DEBUG: 05:08:57.691: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.693: Image device open completed 417s (process:2071): libfprint-device-DEBUG: 05:08:57.693: Device reported open completion 417s (process:2071): libfprint-nb1010-DEBUG: 05:08:57.693: nb1010 Initialized 417s (process:2071): libfprint-device-DEBUG: 05:08:57.693: Completing action FPI_DEVICE_ACTION_OPEN in idle! 417s (process:2071): libfprint-device-DEBUG: 05:08:57.693: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s (process:2071): libfprint-device-DEBUG: 05:08:57.693: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.693: Activating image device 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.693: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.693: Image device activation completed 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.693: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.693: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 417s (process:2071): libfprint-SSM-DEBUG: 05:08:57.693: [nb1010] M_LOOP_NUM_STATES entering state 0 417s (process:2071): libfprint-device-DEBUG: 05:08:57.693: Device reported finger status change: FP_FINGER_STATUS_NEEDED 417s (process:2071): libfprint-nb1010-DEBUG: 05:08:57.693: nb1010 Activated 417s (process:2071): libfprint-SSM-DEBUG: 05:08:57.743: [nb1010] M_LOOP_NUM_STATES entering state 1 417s (process:2071): libfprint-SSM-DEBUG: 05:08:57.744: [nb1010] M_LOOP_NUM_STATES entering state 2 417s (process:2071): libfprint-SSM-DEBUG: 05:08:57.745: [nb1010] M_LOOP_NUM_STATES entering state 3 417s (process:2071): libfprint-device-DEBUG: 05:08:57.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.745: Image device reported finger status: on 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.745: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 417s (process:2071): libfprint-SSM-DEBUG: 05:08:57.746: [nb1010] M_LOOP_NUM_STATES entering state 4 417s (process:2071): libfprint-SSM-DEBUG: 05:08:57.747: [nb1010] M_LOOP_NUM_STATES entering state 5 417s (process:2071): libfprint-device-DEBUG: 05:08:57.793: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 417s (process:2071): libfprint-SSM-DEBUG: 05:08:57.797: [nb1010] M_LOOP_NUM_STATES entering state 6 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.797: Image device captured an image 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.798: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 417s (process:2071): libfprint-device-DEBUG: 05:08:57.798: Device reported finger status change: FP_FINGER_STATUS_PRESENT 417s (process:2071): libfprint-SSM-DEBUG: 05:08:57.798: [nb1010] M_LOOP_NUM_STATES completed successfully 417s (process:2071): libfprint-nb1010-DEBUG: 05:08:57.798: nb1010 ssm complete cb 417s (process:2071): libfprint-device-DEBUG: 05:08:57.798: Device reported finger status change: FP_FINGER_STATUS_NONE 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.798: Image device reported finger status: off 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.798: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.798: Deactivating image device 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.798: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.798: Image device deactivation completed 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.798: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 417s (process:2071): libfprint-nb1010-DEBUG: 05:08:57.798: nb1010 Deactivated 417s (process:2071): libfprint-image-DEBUG: 05:08:57.811: Minutiae scan completed in 0.013276 secs 417s (process:2071): libfprint-device-DEBUG: 05:08:57.812: Device reported capture completion 417s (process:2071): libfprint-device-DEBUG: 05:08:57.812: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 417s (process:2071): libfprint-device-DEBUG: 05:08:57.812: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 417s (process:2071): libfprint-image_device-DEBUG: 05:08:57.812: Image device close completed 417s (process:2071): libfprint-device-DEBUG: 05:08:57.812: Device reported close completion 417s (process:2071): libfprint-nb1010-DEBUG: 05:08:57.812: nb1010 Deinitialized 417s (process:2071): libfprint-device-DEBUG: 05:08:57.812: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 417s (process:2071): libfprint-device-DEBUG: 05:08:57.812: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 417s ** (umockdev-run:2067): DEBUG: 05:08:57.909: umockdev.vala:154: Removing test bed /tmp/umockdev.4OF112 417s (umockdev-run:2067): GLib-DEBUG: 05:08:57.918: unsetenv() is not thread-safe and should not be used after threads are created 417s Comparing PNGs /tmp/libfprint-umockdev-test-kydttdmj/capture.png and /usr/share/installed-tests/libfprint-2/nb1010/capture.png 417s PASS: libfprint-2/driver-nb1010.test 417s Running test: libfprint-2/fpi-device.test 417s Executing: libfprint-2/fpi-device.test 417s TAP version 14 417s # random seed: R02S1885b6b9e445be655c8a7930e803ba3c 417s 1..97 417s # Start of driver tests 417s ok 1 /driver/get_driver 417s ok 2 /driver/get_device_id 417s ok 3 /driver/get_name 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 417s # 417s # libfprint-device-DEBUG: Device reported open completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 417s # 417s # libfprint-device-DEBUG: Device reported close completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s ok 4 /driver/is_open 417s ok 5 /driver/get_nr_enroll_stages 417s ok 6 /driver/set_nr_enroll_stages 417s ok 7 /driver/supports_identify 417s ok 8 /driver/supports_capture 417s ok 9 /driver/has_storage 417s ok 10 /driver/do_not_support_identify 417s ok 11 /driver/do_not_support_capture 417s ok 12 /driver/has_not_storage 417s ok 13 /driver/get_usb_device 417s ok 14 /driver/get_virtual_env 417s ok 15 /driver/get_driver_data 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 417s # 417s # libfprint-device-DEBUG: Device reported probe completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s ok 16 /driver/initial_features 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 417s # 417s # libfprint-device-DEBUG: Device reported probe completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s ok 17 /driver/probe 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 417s # 417s # libfprint-device-DEBUG: Device reported open completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 417s # 417s # libfprint-device-DEBUG: Device reported close completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s ok 18 /driver/open 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 417s # 417s # libfprint-device-DEBUG: Device reported open completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 417s # 417s # libfprint-device-DEBUG: Device reported close completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s ok 19 /driver/close 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 417s # 417s # libfprint-device-DEBUG: Device reported open completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 417s # 417s # libfprint-device-DEBUG: Device reported enroll completion 417s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 417s # 417s # libfprint-device-DEBUG: Device reported close completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 417s ok 20 /driver/enroll 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 417s # 417s # libfprint-device-DEBUG: Device reported open completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 417s # 417s # libfprint-device-DEBUG: Device reported verify result 417s # libfprint-device-DEBUG: Device reported verify completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 417s # 417s # libfprint-device-DEBUG: Device reported close completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 417s ok 21 /driver/verify 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 417s # 417s # libfprint-device-DEBUG: Device reported open completion 417s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 417s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 417s # 417s # 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-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-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 23 /driver/capture 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 24 /driver/list 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 25 /driver/delete 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 26 /driver/clear_storage 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: Idle cancelling on ongoing operation! 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 418s # 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.10 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 27 /driver/cancel 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-device-DEBUG: Idle cancelling on ongoing operation! 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 418s # 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 418s # 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 418s # 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 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-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 28 /driver/critical 418s ok 29 /driver/get_current_action 418s ok 30 /driver/timeout 418s ok 31 /driver/error_types 418s ok 32 /driver/retry_error_types 418s # Start of get_scan_type tests 418s ok 33 /driver/get_scan_type/press 418s ok 34 /driver/get_scan_type/swipe 418s # End of get_scan_type tests 418s # Start of set_scan_type tests 418s ok 35 /driver/set_scan_type/press 418s ok 36 /driver/set_scan_type/swipe 418s # End of set_scan_type tests 418s # Start of finger_status tests 418s ok 37 /driver/finger_status/inactive 418s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 418s ok 38 /driver/finger_status/waiting 418s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 418s ok 39 /driver/finger_status/present 418s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 418s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 418s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 418s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 418s ok 40 /driver/finger_status/changes 418s # End of finger_status tests 418s # Start of features tests 418s # libfprint-fake_test_dev-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 ok 41 /driver/features/probe_updates 418s # End of features tests 418s # Start of initial_features tests 418s ok 42 /driver/initial_features/none 418s ok 43 /driver/initial_features/no_capture 418s ok 44 /driver/initial_features/no_verify 418s ok 45 /driver/initial_features/no_identify 418s ok 46 /driver/initial_features/no_storage 418s ok 47 /driver/initial_features/no_list 418s ok 48 /driver/initial_features/no_delete 418s ok 49 /driver/initial_features/no_clear 418s # End of initial_features tests 418s # Start of probe tests 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 50 /driver/probe/error 418s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 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 51 /driver/probe/action_error 418s # End of probe tests 418s # Start of open 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 ok 52 /driver/open/error 418s # End of open tests 418s # Start of close 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 53 /driver/close/error 418s # End of close tests 418s # Start of enroll 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-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-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 54 /driver/enroll/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-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-device-DEBUG: Device reported enroll progress, reported 1959043123 of 1392898800 have been completed 418s # libfprint-device-DEBUG: Device reported enroll progress, reported 1931953736 of 1392898800 have been completed 418s # libfprint-device-DEBUG: Device reported enroll progress, reported 1695596048 of 1392898800 have been completed 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: 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-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 55 /driver/enroll/progress 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: 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-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 56 /driver/enroll/update_nbis 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 57 /driver/enroll/update_nbis_wrong_device 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 58 /driver/enroll/update_nbis_wrong_driver 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 59 /driver/enroll/update_nbis_missing_feature 418s # Start of error 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-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-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-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_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-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_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 60 /driver/enroll/error/no_print 418s # End of error tests 418s # End of enroll tests 418s # Start of verify 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-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_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-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 61 /driver/verify/fail 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_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-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 62 /driver/verify/retry 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_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_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 63 /driver/verify/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 64 /driver/verify/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-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-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 65 /driver/verify/report_no_cb 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-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-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 66 /driver/verify/not_reported 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-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-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-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_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-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_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-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_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-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_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 67 /driver/verify/complete_retry 418s # End of verify tests 418s # Start of identify 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-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_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.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_COLD 418s ok 68 /driver/identify/fail 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_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.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_COLD 418s ok 69 /driver/identify/retry 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_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_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_COLD 418s ok 70 /driver/identify/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-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-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_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_COLD 418s ok 71 /driver/identify/not_reported 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-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.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-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.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-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.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 72 /driver/identify/complete_retry 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-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.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 73 /driver/identify/report_no_cb 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_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 418s # 418s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 418s # 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 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-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 74 /driver/identify/suspend_continues 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_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 418s # 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 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-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 75 /driver/identify/suspend_succeeds 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_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 418s # 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_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 76 /driver/identify/suspend_busy_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 77 /driver/identify/suspend_while_idle 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-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 420s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 420s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 420s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 420s # 420s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 420s # 420s # libfprint-device-DEBUG: Device reported identify completion 420s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 420s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 420s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 420s # 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 # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 422s Executing: libfprint-2/fpi-device.test 425s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 78 /driver/identify/warmup_cooldown 425s # slow test /driver/identify/warmup_cooldown executed in 7.30 secs 425s # End of identify tests 425s # Start of capture tests 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 79 /driver/capture/not_supported 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 425s # 425s # libfprint-device-DEBUG: Device reported capture completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s ok 80 /driver/capture/error 425s # End of capture tests 425s # Start of list tests 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 425s # 425s # libfprint-device-DEBUG: Device reported listing completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 81 /driver/list/error 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 82 /driver/list/no_storage 425s # End of list tests 425s # Start of delete tests 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 425s # 425s # libfprint-device-DEBUG: Device reported deletion completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 83 /driver/delete/error 425s # End of delete tests 425s # Start of clear_storage tests 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 425s # 425s # libfprint-device-DEBUG: Device reported deletion completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 84 /driver/clear_storage/error 425s # End of clear_storage tests 425s # Start of cancel tests 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 425s # 425s # libfprint-device-DEBUG: Device reported deletion completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 85 /driver/cancel/fail 425s # End of cancel tests 425s # Start of get_current_action tests 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 86 /driver/get_current_action/open 425s # End of get_current_action tests 425s # Start of get_cancellable tests 425s ok 87 /driver/get_cancellable/error 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 88 /driver/get_cancellable/open 425s # Start of open tests 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 89 /driver/get_cancellable/open/internal 425s # End of open tests 425s # End of get_cancellable tests 425s # Start of action_is_cancelled tests 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 90 /driver/action_is_cancelled/open 425s ok 91 /driver/action_is_cancelled/error 425s # Start of open tests 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 92 /driver/action_is_cancelled/open/internal 425s # End of open tests 425s # End of action_is_cancelled tests 425s # Start of complete_action tests 425s # Start of all tests 425s ok 93 /driver/complete_action/all/error 425s # End of all tests 425s # End of complete_action tests 425s # Start of action_error tests 425s ok 94 /driver/action_error/error 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 425s # 425s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 425s # libfprint-device-DEBUG: Device reported enroll completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 425s # 425s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 425s # libfprint-device-DEBUG: Device reported verify completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 425s # 425s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 425s # libfprint-device-DEBUG: Device reported identify completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 425s # 425s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 425s # libfprint-device-DEBUG: Device reported capture completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 425s # 425s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 425s # libfprint-device-DEBUG: Device reported listing completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 425s # 425s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 425s # libfprint-device-DEBUG: Device reported deletion completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 425s # 425s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 425s # libfprint-device-DEBUG: Device reported deletion completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s ok 95 /driver/action_error/all 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 425s # 425s # libfprint-device-DEBUG: Device reported enroll completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 425s # 425s # libfprint-device-DEBUG: Device reported verify completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 425s # 425s # libfprint-device-DEBUG: Device reported identify completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 425s # 425s # libfprint-device-DEBUG: Device reported capture completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 425s # 425s # libfprint-device-DEBUG: Device reported listing completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 425s # 425s # libfprint-device-DEBUG: Device reported deletion completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 425s # 425s # libfprint-device-DEBUG: Device reported deletion completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s ok 96 /driver/action_error/fail 425s # End of action_error tests 425s # Start of timeout tests 425s ok 97 /driver/timeout/cancelled 425s # End of timeout tests 425s # End of driver tests 425s PASS: libfprint-2/fpi-device.test 425s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 425s TAP version 14 425s # random seed: R02S278e30bb30f4b61fbb3c98493e31bda0 425s 1..14 425s # Start of device tests 425s # Start of async tests 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 1 /device/async/open 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 2 /device/async/close 425s # End of async tests 425s # Start of sync tests 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 3 /device/sync/open 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 4 /device/sync/close 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 5 /device/sync/get_driver 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 6 /device/sync/get_device_id 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 7 /device/sync/get_name 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 8 /device/sync/get_scan_type 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 9 /device/sync/get_nr_enroll_stages 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 10 /device/sync/supports_identify 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 11 /device/sync/supports_capture 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 12 /device/sync/has_storage 425s # Start of open tests 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 13 /device/sync/open/notify 425s # End of open tests 425s # Start of close tests 425s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 425s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 425s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf0431a45, GType is 119587224 425s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 425s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 425s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 425s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 425s # libfprint-context-DEBUG: created 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 425s # 425s # libfprint-device-DEBUG: Device reported probe completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 425s # 425s # libfprint-device-DEBUG: Device reported open completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 425s # 425s # libfprint-device-DEBUG: Device reported close completion 425s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s ok 14 /device/sync/close/notify 425s # End of close tests 425s # End of sync tests 425s # End of device tests 425s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 425s Running test: libfprint-2/driver-egismoc-05a1.test 425s ** (umockdev-run:2116): DEBUG: 05:09:05.613: umockdev.vala:127: Created udev test bed /tmp/umockdev.QBPZ12 425s ** (umockdev-run:2116): DEBUG: 05:09:05.613: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-5 425s ** (umockdev-run:2116): DEBUG: 05:09:05.615: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-5 (subsystem usb) 425s ** (umockdev-run:2116): DEBUG: 05:09:05.620: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.QBPZ12/dev/bus/usb/001/003 425s ** (umockdev-run:2116): DEBUG: 05:09:05.620: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 425s ** (umockdev-run:2116): DEBUG: 05:09:05.622: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 425s ** (umockdev-run:2116): DEBUG: 05:09:05.626: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.QBPZ12/dev/bus/usb/001/001 425s ** (umockdev-run:2116): DEBUG: 05:09:05.626: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 425s ** (umockdev-run:2116): DEBUG: 05:09:05.626: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 425s (process:2120): libfprint-context-DEBUG: 05:09:05.734: Initializing FpContext (libfprint version 1.94.9+tod1) 425s (process:2120): libfprint-tod-DEBUG: 05:09:05.734: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.737: 131004731045: ../libfprint/drivers/egismoc/egismoc.c:1597 425s (process:2120): libfprint-context-DEBUG: 05:09:05.737: No driver found for USB device 1D6B:0002 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.737: egismoc_probe enter --> 425s (process:2120): libfprint-device-DEBUG: 05:09:05.740: Device reported probe completion 425s (process:2120): libfprint-device-DEBUG: 05:09:05.740: Completing action FPI_DEVICE_ACTION_PROBE in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.740: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.741: Opening device 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.742: [egismoc] DEV_INIT_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.743: [egismoc] DEV_INIT_STATES entering state 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.744: [egismoc] DEV_INIT_STATES entering state 2 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.745: [egismoc] DEV_INIT_STATES entering state 3 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.745: [egismoc] DEV_INIT_STATES entering state 4 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.746: [egismoc] DEV_INIT_STATES entering state 5 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.746: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.746: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.746: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.747: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.748: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.748: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.748: Firmware version callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.748: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.748: Device firmware version is 9050.1.2.13 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.748: [egismoc] DEV_INIT_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.748: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.748: Device reported open completion 425s (process:2120): libfprint-device-DEBUG: 05:09:05.748: Completing action FPI_DEVICE_ACTION_OPEN in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.748: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.748: List 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.748: [egismoc] LIST_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.748: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.748: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.748: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.749: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.750: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.750: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.750: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.750: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.750: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.750: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.750: Number of currently enrolled fingerprints on the device is 3 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.750: [egismoc] LIST_STATES entering state 1 425s (process:2120): libfprint-device-DEBUG: 05:09:05.750: Device reported listing completion 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.750: [egismoc] LIST_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.750: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.750: Completing action FPI_DEVICE_ACTION_LIST in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.750: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.750: Clear storage 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.750: [egismoc] DELETE_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.750: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.750: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.750: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.751: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.752: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.752: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.752: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.752: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.752: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.752: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.752: Number of currently enrolled fingerprints on the device is 3 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.752: [egismoc] DELETE_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.752: Get delete command 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.752: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.752: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.752: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.753: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.753: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.753: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.753: Delete callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.753: Response prefix valid: yes 425s (process:2120): libfprint-device-DEBUG: 05:09:05.753: Device reported deletion completion 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.753: [egismoc] DELETE_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.753: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.753: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.753: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.754: List 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.754: [egismoc] LIST_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.754: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.754: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.754: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.754: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.755: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.755: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.755: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.755: Number of currently enrolled fingerprints on the device is 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.755: [egismoc] LIST_STATES entering state 1 425s (process:2120): libfprint-device-DEBUG: 05:09:05.755: Device reported listing completion 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.755: [egismoc] LIST_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.755: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.755: Completing action FPI_DEVICE_ACTION_LIST in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.755: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s (process:2120): libfprint-device-DEBUG: 05:09:05.756: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.756: Enroll 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.756: [egismoc] ENROLL_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.756: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.756: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.756: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.756: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.758: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.758: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.758: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.758: Number of currently enrolled fingerprints on the device is 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.758: [egismoc] ENROLL_STATES entering state 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.758: [egismoc] ENROLL_STATES entering state 2 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.758: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.758: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.758: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.759: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.760: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.760: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.760: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.760: [egismoc] ENROLL_STATES entering state 3 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.760: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.760: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.760: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.761: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.762: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.762: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.762: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.762: [egismoc] ENROLL_STATES entering state 4 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.762: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.762: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.763: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.763: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.763: [egismoc] ENROLL_STATES entering state 5 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.763: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.763: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.763: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.764: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.765: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.765: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.765: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.765: [egismoc] ENROLL_STATES entering state 6 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.765: Get check command 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.765: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.765: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.765: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.765: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.766: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.766: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.766: Enroll check callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.766: Response suffix valid: yes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.766: [egismoc] ENROLL_STATES entering state 7 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.766: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.766: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.766: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.767: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.768: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.768: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.768: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.768: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.768: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.768: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.768: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.769: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.769: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.769: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.769: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.769: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.769: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.769: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.769: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.770: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.771: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.771: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.771: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.771: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.771: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.771: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.772: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.772: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.772: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.772: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.772: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.772: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.772: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.773: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.773: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.773: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.773: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.773: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.773: Partial capture successful. Please touch the sensor again (1/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.773: Device reported enroll progress, reported 1 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.773: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.773: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.773: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.773: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.774: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.775: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.775: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.775: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.775: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.775: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.775: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.775: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.776: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.776: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.776: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.776: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.776: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.776: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.776: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.777: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.777: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.777: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.777: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.777: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.777: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.778: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.779: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.779: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.779: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.779: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.779: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.779: Partial capture successful. Please touch the sensor again (2/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.779: Device reported enroll progress, reported 2 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.779: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.779: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.779: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.779: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.780: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.780: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.780: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.780: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.780: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.780: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.780: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.780: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.781: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.782: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.782: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.782: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.782: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.782: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.783: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.783: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.783: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.783: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.783: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.783: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.783: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.784: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.784: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.784: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.784: Response prefix valid: NO 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.784: Response prefix valid: NO 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.784: Response prefix valid: yes 425s (process:2120): libfprint-device-DEBUG: 05:09:05.784: Device reported enroll progress, reported 2 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.784: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.784: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.784: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.784: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.785: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.786: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.786: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.786: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.786: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.786: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.786: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.786: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.786: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.787: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.787: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.787: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.787: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.787: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.787: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.788: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.788: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.788: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.788: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.788: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.788: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.789: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.790: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.790: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.790: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.790: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.790: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.790: Partial capture successful. Please touch the sensor again (3/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.790: Device reported enroll progress, reported 3 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.790: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.790: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.790: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.790: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.790: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.791: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.791: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.791: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.791: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.791: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.791: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.791: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.792: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.793: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.793: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.793: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.793: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.793: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.793: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.793: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.793: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.793: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.793: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.793: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.793: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.794: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.795: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.795: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.795: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.795: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.795: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.795: Partial capture successful. Please touch the sensor again (4/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.795: Device reported enroll progress, reported 4 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.795: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.795: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.795: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.795: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.796: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.796: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.796: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.796: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.796: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.796: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.796: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.796: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.797: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.798: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.798: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.798: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.798: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.798: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.799: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.799: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.799: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.799: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.799: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.799: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.799: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.800: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.800: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.800: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.800: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.800: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.800: Partial capture successful. Please touch the sensor again (5/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.800: Device reported enroll progress, reported 5 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.800: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.800: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.800: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.800: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.801: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.802: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.802: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.802: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.802: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.802: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.802: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.802: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.803: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.804: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.804: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.804: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.804: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.804: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.804: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.804: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.804: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.804: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.804: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.804: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.804: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.805: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.806: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.806: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.806: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.806: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.806: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.806: Partial capture successful. Please touch the sensor again (6/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.806: Device reported enroll progress, reported 6 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.806: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.806: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.806: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.806: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.807: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.807: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.807: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.807: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.807: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.807: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.807: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.807: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.808: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.809: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.809: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.809: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.809: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.809: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.810: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.810: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.810: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.810: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.810: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.810: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.811: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.811: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.811: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.811: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.811: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.811: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.811: Partial capture successful. Please touch the sensor again (7/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.811: Device reported enroll progress, reported 7 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.811: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.811: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.811: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.811: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.812: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.813: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.813: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.813: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.813: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.813: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.813: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.813: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.814: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.815: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.815: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.815: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.815: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.815: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.815: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.815: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.815: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.815: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.815: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.815: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.815: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.816: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.817: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.817: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.817: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.817: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.817: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.817: Partial capture successful. Please touch the sensor again (8/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.817: Device reported enroll progress, reported 8 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.817: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.817: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.817: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.817: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.817: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.818: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.818: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.818: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.818: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.818: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.818: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.818: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.819: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.820: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.820: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.820: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.820: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.820: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.821: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.821: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.821: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.821: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.821: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.821: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.821: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.822: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.822: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.822: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.822: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.822: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.822: Partial capture successful. Please touch the sensor again (9/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.822: Device reported enroll progress, reported 9 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.822: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.822: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.822: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.822: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.823: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.824: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.824: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.824: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.824: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.824: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.824: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.824: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.824: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.825: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.825: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.825: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.825: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.825: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.825: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.826: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.826: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.826: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.826: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.826: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.826: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.827: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.827: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.827: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.827: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.827: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.827: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.827: Partial capture successful. Please touch the sensor again (10/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.827: Device reported enroll progress, reported 10 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.827: [egismoc] ENROLL_STATES entering state 12 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.827: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.827: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.827: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.828: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.829: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.829: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.829: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.829: [egismoc] ENROLL_STATES entering state 13 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.829: New fingerprint ID: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.829: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.829: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.829: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.830: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.830: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.830: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.830: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.830: [egismoc] ENROLL_STATES entering state 14 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.830: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.830: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.830: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.831: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.832: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.832: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.832: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.832: [egismoc] ENROLL_STATES entering state 15 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.832: Enrollment was successful! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.832: Device reported enroll completion 425s (process:2120): libfprint-device-DEBUG: 05:09:05.832: Device reported finger status change: FP_FINGER_STATUS_NONE 425s (process:2120): libfprint-device-DEBUG: 05:09:05.832: Print for finger FP_FINGER_LEFT_INDEX enrolled 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.832: [egismoc] ENROLL_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.832: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.832: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.832: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.832: List 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.832: [egismoc] LIST_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.832: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.832: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.832: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.833: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.833: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.834: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.834: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.834: Device fingerprint 1: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.834: Number of currently enrolled fingerprints on the device is 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.834: [egismoc] LIST_STATES entering state 1 425s (process:2120): libfprint-device-DEBUG: 05:09:05.834: Device reported listing completion 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.834: [egismoc] LIST_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.834: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.834: Completing action FPI_DEVICE_ACTION_LIST in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.834: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-device-DEBUG: 05:09:05.834: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.834: Identify or Verify 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.834: [egismoc] IDENTIFY_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.834: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.834: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.834: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.835: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.836: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.836: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.836: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.836: Device fingerprint 1: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.836: Number of currently enrolled fingerprints on the device is 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.836: [egismoc] IDENTIFY_STATES entering state 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.836: [egismoc] IDENTIFY_STATES entering state 2 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.836: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.836: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.836: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.836: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.837: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.837: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.837: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.837: [egismoc] IDENTIFY_STATES entering state 3 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.837: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.837: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.837: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.838: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.839: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.839: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.839: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.839: [egismoc] IDENTIFY_STATES entering state 4 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.839: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.839: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.839: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.839: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.839: [egismoc] IDENTIFY_STATES entering state 5 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.840: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.840: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.840: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.840: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.841: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.841: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.841: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.841: [egismoc] IDENTIFY_STATES entering state 6 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.841: Get check command 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.841: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.841: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.841: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.842: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.843: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.843: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.843: Identify check callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.843: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.843: Identify successful for: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.843: Verifying against: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-device-DEBUG: 05:09:05.843: Device reported verify result 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.843: [egismoc] IDENTIFY_STATES entering state 7 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.843: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.843: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.843: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.843: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.844: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.844: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.844: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.844: [egismoc] IDENTIFY_STATES entering state 8 425s (process:2120): libfprint-device-DEBUG: 05:09:05.844: Device reported verify completion 425s (process:2120): libfprint-device-DEBUG: 05:09:05.844: Device reported finger status change: FP_FINGER_STATUS_NONE 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.844: [egismoc] IDENTIFY_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.844: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.844: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.844: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-device-DEBUG: 05:09:05.845: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.845: Identify or Verify 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.845: [egismoc] IDENTIFY_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.845: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.845: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.845: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.846: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.846: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.846: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.846: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.846: Device fingerprint 1: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.846: Number of currently enrolled fingerprints on the device is 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.846: [egismoc] IDENTIFY_STATES entering state 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.846: [egismoc] IDENTIFY_STATES entering state 2 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.846: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.846: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.846: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.847: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.848: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.848: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.848: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.848: [egismoc] IDENTIFY_STATES entering state 3 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.848: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.848: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.848: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.849: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.849: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.849: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.849: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.849: [egismoc] IDENTIFY_STATES entering state 4 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.849: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.849: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.850: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.850: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.850: [egismoc] IDENTIFY_STATES entering state 5 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.850: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.850: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.850: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.851: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.852: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.852: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.852: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.852: [egismoc] IDENTIFY_STATES entering state 6 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.852: Get check command 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.852: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.852: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.852: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.852: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.853: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.853: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.853: Identify check callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.853: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.853: Identify successful for: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-device-DEBUG: 05:09:05.853: Device reported identify result 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.853: [egismoc] IDENTIFY_STATES entering state 7 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.853: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.853: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.853: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.854: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.855: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.855: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.855: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.855: [egismoc] IDENTIFY_STATES entering state 8 425s (process:2120): libfprint-device-DEBUG: 05:09:05.855: Device reported identify completion 425s (process:2120): libfprint-device-DEBUG: 05:09:05.855: Device reported finger status change: FP_FINGER_STATUS_NONE 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.855: [egismoc] IDENTIFY_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.855: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.855: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.855: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-device-DEBUG: 05:09:05.856: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.856: Enroll 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.856: [egismoc] ENROLL_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.856: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.856: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.856: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.856: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.857: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.857: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.857: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.857: Device fingerprint 1: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.857: Number of currently enrolled fingerprints on the device is 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.857: [egismoc] ENROLL_STATES entering state 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.857: [egismoc] ENROLL_STATES entering state 2 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.857: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.857: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.857: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.858: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.859: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.859: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.859: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.859: [egismoc] ENROLL_STATES entering state 3 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.859: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.859: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.859: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.859: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.860: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.860: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.860: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.860: [egismoc] ENROLL_STATES entering state 4 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.860: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.860: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.861: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.861: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.861: [egismoc] ENROLL_STATES entering state 5 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.861: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.861: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.861: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.861: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.862: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.862: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.862: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.862: [egismoc] ENROLL_STATES entering state 6 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.862: Get check command 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.862: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.862: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.862: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.863: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.864: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.864: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.864: Enroll check callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.864: Response suffix valid: NO 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.864: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.864: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.864: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.864: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 425s (process:2120): libfprint-device-DEBUG: 05:09:05.864: Device reported enroll completion 425s (process:2120): libfprint-device-DEBUG: 05:09:05.864: Device reported finger status change: FP_FINGER_STATUS_NONE 425s (process:2120): libfprint-device-DEBUG: 05:09:05.864: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.864: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.864: List 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.864: [egismoc] LIST_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.864: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.864: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.864: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.865: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.866: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.866: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.866: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.866: Device fingerprint 1: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.866: Number of currently enrolled fingerprints on the device is 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.866: [egismoc] LIST_STATES entering state 1 425s (process:2120): libfprint-device-DEBUG: 05:09:05.866: Device reported listing completion 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.866: [egismoc] LIST_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.866: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.866: Completing action FPI_DEVICE_ACTION_LIST in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.866: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-device-DEBUG: 05:09:05.866: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.866: Enroll 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.866: [egismoc] ENROLL_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.866: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.866: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.866: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.867: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.868: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.868: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.868: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.868: Device fingerprint 1: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.868: Number of currently enrolled fingerprints on the device is 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.868: [egismoc] ENROLL_STATES entering state 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.868: [egismoc] ENROLL_STATES entering state 2 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.868: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.868: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.868: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.868: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.869: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.869: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.869: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.869: [egismoc] ENROLL_STATES entering state 3 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.869: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.869: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.869: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.870: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.871: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.871: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.871: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.871: [egismoc] ENROLL_STATES entering state 4 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.871: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.871: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.872: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.872: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.872: [egismoc] ENROLL_STATES entering state 5 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.872: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.872: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.872: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.872: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.873: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.873: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.873: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.873: [egismoc] ENROLL_STATES entering state 6 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.873: Get check command 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.873: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.873: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.873: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.874: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.875: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.875: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.875: Enroll check callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.875: Response suffix valid: yes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.875: [egismoc] ENROLL_STATES entering state 7 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.875: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.875: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.875: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.875: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.876: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.876: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.876: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.876: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.876: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.876: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.876: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.877: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.878: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.878: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.878: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.878: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.878: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.878: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.878: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.878: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.879: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.879: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.879: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.879: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.879: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.880: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.880: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.880: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.880: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.880: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.880: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.881: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.881: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.881: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.881: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.881: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.881: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.881: Partial capture successful. Please touch the sensor again (1/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.881: Device reported enroll progress, reported 1 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.881: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.881: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.881: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.881: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.882: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.883: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.883: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.883: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.883: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.883: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.883: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.883: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.884: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.885: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.885: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.885: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.885: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.885: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.885: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.886: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.886: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.886: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.886: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.886: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.886: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.886: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.887: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.887: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.887: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.887: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.887: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.887: Partial capture successful. Please touch the sensor again (2/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.887: Device reported enroll progress, reported 2 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.887: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.887: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.887: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.887: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.888: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.889: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.889: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.889: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.889: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.889: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.889: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.889: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.889: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.890: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.890: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.890: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.890: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.890: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.890: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.891: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.891: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.891: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.891: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.891: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.891: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.892: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.892: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.892: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.892: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.892: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.892: Response suffix valid: NO 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.892: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.892: Response suffix valid: yes 425s (process:2120): libfprint-device-DEBUG: 05:09:05.892: Device reported enroll progress, reported 2 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.892: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.892: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.892: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.892: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.893: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.894: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.894: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.894: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.894: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.894: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.894: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.894: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.895: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.895: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.895: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.895: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.895: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.895: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.895: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.896: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.896: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.896: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.896: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.896: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.896: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.897: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.898: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.898: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.898: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.898: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.898: Response suffix valid: NO 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.898: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.898: Response suffix valid: yes 425s (process:2120): libfprint-device-DEBUG: 05:09:05.898: Device reported enroll progress, reported 2 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.898: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.898: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.898: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.898: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.898: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.899: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.899: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.899: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.899: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.899: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.899: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.899: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.900: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.901: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.901: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.901: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.901: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.901: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.901: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.901: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.901: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.901: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.901: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.901: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.902: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.903: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.903: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.903: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.903: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.903: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.903: Partial capture successful. Please touch the sensor again (3/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.903: Device reported enroll progress, reported 3 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.903: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.903: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.903: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.903: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.904: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.904: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.904: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.904: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.904: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.904: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.904: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.904: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.905: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.906: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.906: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.906: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.906: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.906: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.906: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.907: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.907: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.907: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.907: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.907: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.907: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.907: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.908: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.908: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.908: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.908: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.908: Response suffix valid: NO 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.908: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.908: Response suffix valid: yes 425s (process:2120): libfprint-device-DEBUG: 05:09:05.908: Device reported enroll progress, reported 3 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.908: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.908: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.908: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.908: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.909: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.910: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.910: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.910: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.910: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.910: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.910: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.910: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.910: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.911: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.911: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.911: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.911: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.911: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.912: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.912: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.912: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.912: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.912: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.912: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.913: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.913: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.913: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.913: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.913: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.913: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.913: Partial capture successful. Please touch the sensor again (4/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.913: Device reported enroll progress, reported 4 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.914: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.914: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.914: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.914: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.914: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.915: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.915: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.915: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.915: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.915: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.915: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.915: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.916: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.916: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.916: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.916: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.916: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.916: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.916: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.917: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.917: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.917: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.917: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.917: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.917: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.918: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.919: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.919: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.919: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.919: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.919: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.919: Partial capture successful. Please touch the sensor again (5/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.919: Device reported enroll progress, reported 5 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.919: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.919: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.919: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.919: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.919: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.920: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.920: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.920: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.920: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.920: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.920: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.920: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.921: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.922: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.922: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.922: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.922: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.922: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.922: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.922: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.922: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.922: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.922: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.922: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.922: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.923: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.925: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.925: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.925: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.925: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.925: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.925: Partial capture successful. Please touch the sensor again (6/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.925: Device reported enroll progress, reported 6 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.925: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.925: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.925: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.925: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.925: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.926: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.926: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.926: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.926: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.926: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.926: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.926: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.927: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.928: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.928: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.928: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.928: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.928: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.928: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.928: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.928: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.928: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.928: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.928: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.928: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.929: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.930: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.930: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.930: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.930: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.930: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.930: Partial capture successful. Please touch the sensor again (7/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.930: Device reported enroll progress, reported 7 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.930: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.930: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.930: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.930: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.931: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.932: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.932: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.932: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.932: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.932: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.932: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.932: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.932: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.933: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.933: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.933: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.933: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.933: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.933: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.934: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.934: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.934: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.934: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.934: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.934: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.935: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.935: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.935: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.935: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.935: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.935: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.935: Partial capture successful. Please touch the sensor again (8/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.935: Device reported enroll progress, reported 8 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.935: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.935: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.936: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.936: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.936: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.937: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.937: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.937: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.937: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.937: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.937: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.937: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.938: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.939: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.939: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.939: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.939: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.939: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.939: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.939: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.939: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.939: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.939: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.939: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.939: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.940: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.941: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.941: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.941: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.941: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.941: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.941: Partial capture successful. Please touch the sensor again (9/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.941: Device reported enroll progress, reported 9 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.941: [egismoc] ENROLL_STATES entering state 8 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.941: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.941: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.941: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.942: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.943: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.943: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.943: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.943: [egismoc] ENROLL_STATES entering state 9 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.943: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.943: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.943: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.943: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.944: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.944: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.944: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.944: [egismoc] ENROLL_STATES entering state 10 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.944: Wait for finger on sensor 425s (process:2120): libfprint-device-DEBUG: 05:09:05.944: Device reported finger status change: FP_FINGER_STATUS_NEEDED 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.945: Finger on sensor callback 425s (process:2120): libfprint-device-DEBUG: 05:09:05.945: Device reported finger status change: FP_FINGER_STATUS_PRESENT 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.945: [egismoc] ENROLL_STATES entering state 11 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.945: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.945: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.945: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.946: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.946: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.946: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.946: Read capture callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.946: Response prefix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.946: Response suffix valid: yes 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.946: Partial capture successful. Please touch the sensor again (10/10) 425s (process:2120): libfprint-device-DEBUG: 05:09:05.946: Device reported enroll progress, reported 10 of 10 have been completed 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.946: [egismoc] ENROLL_STATES entering state 12 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.946: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.947: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.947: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.947: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.948: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.948: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.948: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.948: [egismoc] ENROLL_STATES entering state 13 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.948: New fingerprint ID: FP1-00000000-7-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.948: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.948: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.948: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.949: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.949: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.949: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.949: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.949: [egismoc] ENROLL_STATES entering state 14 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.949: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.949: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.949: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.950: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.951: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.951: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.951: Task SSM next state callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.951: [egismoc] ENROLL_STATES entering state 15 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.951: Enrollment was successful! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.951: Device reported enroll completion 425s (process:2120): libfprint-device-DEBUG: 05:09:05.951: Device reported finger status change: FP_FINGER_STATUS_NONE 425s (process:2120): libfprint-device-DEBUG: 05:09:05.951: Print for finger FP_FINGER_RIGHT_INDEX enrolled 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.951: [egismoc] ENROLL_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.951: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.951: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.951: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.951: List 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.951: [egismoc] LIST_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.951: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.951: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.951: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.952: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.953: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.953: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.953: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.953: Device fingerprint 1: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.953: Device fingerprint 2: FP1-00000000-7-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.953: Number of currently enrolled fingerprints on the device is 2 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.953: [egismoc] LIST_STATES entering state 1 425s (process:2120): libfprint-device-DEBUG: 05:09:05.953: Device reported listing completion 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.953: [egismoc] LIST_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.953: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.953: Completing action FPI_DEVICE_ACTION_LIST in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.953: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.953: Delete 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.953: [egismoc] DELETE_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.953: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.953: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.953: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.953: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.954: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.954: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.954: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.954: Device fingerprint 1: FP1-00000000-2-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.954: Device fingerprint 2: FP1-00000000-7-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.954: Number of currently enrolled fingerprints on the device is 2 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.954: [egismoc] DELETE_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.954: Get delete command 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.954: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.954: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.954: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.954: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.955: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.956: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.956: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.956: Delete callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.956: Response prefix valid: yes 425s (process:2120): libfprint-device-DEBUG: 05:09:05.956: Device reported deletion completion 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.956: [egismoc] DELETE_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.956: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.956: Completing action FPI_DEVICE_ACTION_DELETE in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.956: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.956: List 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.956: [egismoc] LIST_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.956: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.956: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.956: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.956: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.957: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.957: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.957: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.957: Device fingerprint 1: FP1-00000000-7-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.957: Number of currently enrolled fingerprints on the device is 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.957: [egismoc] LIST_STATES entering state 1 425s (process:2120): libfprint-device-DEBUG: 05:09:05.957: Device reported listing completion 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.957: [egismoc] LIST_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.957: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.957: Completing action FPI_DEVICE_ACTION_LIST in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.957: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.957: Clear storage 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.957: [egismoc] DELETE_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.958: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.958: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.958: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.958: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.959: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.959: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.959: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.959: Device fingerprint 1: FP1-00000000-7-00000000-nobody 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.959: Number of currently enrolled fingerprints on the device is 1 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.959: [egismoc] DELETE_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.959: Get delete command 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.959: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.959: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.959: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.960: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.961: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.961: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.961: Delete callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.961: Response prefix valid: yes 425s (process:2120): libfprint-device-DEBUG: 05:09:05.961: Device reported deletion completion 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.961: [egismoc] DELETE_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.961: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.961: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.961: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.961: List 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.961: [egismoc] LIST_STATES entering state 0 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.961: Execute command and get response 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.961: Get check bytes 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.961: [egismoc] CMD_STATES entering state 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.961: [egismoc] CMD_STATES entering state 1 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.962: Command receive callback 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.962: [egismoc] CMD_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.962: List callback 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.962: Number of currently enrolled fingerprints on the device is 0 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.962: [egismoc] LIST_STATES entering state 1 425s (process:2120): libfprint-device-DEBUG: 05:09:05.962: Device reported listing completion 425s (process:2120): libfprint-SSM-DEBUG: 05:09:05.962: [egismoc] LIST_STATES completed successfully 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.962: Task SSM done 425s (process:2120): libfprint-device-DEBUG: 05:09:05.962: Completing action FPI_DEVICE_ACTION_LIST in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.962: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.962: Closing device 425s (process:2120): libfprint-egismoc-DEBUG: 05:09:05.962: Cancel 425s (process:2120): libfprint-device-DEBUG: 05:09:05.962: Device reported close completion 425s (process:2120): libfprint-device-DEBUG: 05:09:05.963: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 425s (process:2120): libfprint-device-DEBUG: 05:09:05.963: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 425s listing - device should have prints 425s clear device storage 425s clear done 425s listing - device should be empty 425s enrolling 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 1, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 2, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 2, None, None, GLib.Error('Your device is having trouble recognizing you. Make sure your sensor is clean.', 'fp - device - retry - quark', 3)) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 3, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 4, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 5, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 6, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 7, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 8, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 9, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 10, , None, None) 425s enroll done 425s listing - device should have 1 print 425s verifying 425s verify done 425s async identifying 425s indentification_done: 425s try to enroll duplicate 425s duplicate enroll attempt done 425s listing - device should still only have 1 print 425s enroll new finger 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 1, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 2, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 3, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 4, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 5, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 6, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 7, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 8, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 9, , None, None) 425s finger status: 425s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf648f888 (FpiDeviceEgisMoc at 0x87bd80)>, 10, , None, None) 425s enroll new finger done 425s listing - device should have 2 prints 425s deleting first print 425s delete done 425s listing - device should only have second print 425s clear device storage 425s clear done 425s listing - device should be empty 426s ** (umockdev-run:2116): DEBUG: 05:09:05.991: umockdev.vala:154: Removing test bed /tmp/umockdev.QBPZ12 426s (umockdev-run:2116): GLib-DEBUG: 05:09:05.999: 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-elanmoc.test 426s ** (umockdev-run:2128): DEBUG: 05:09:06.060: umockdev.vala:127: Created udev test bed /tmp/umockdev.75AD22 426s ** (umockdev-run:2128): DEBUG: 05:09:06.060: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 426s ** (umockdev-run:2128): DEBUG: 05:09:06.062: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 426s ** (umockdev-run:2128): DEBUG: 05:09:06.067: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.75AD22/dev/bus/usb/001/003 426s ** (umockdev-run:2128): DEBUG: 05:09:06.067: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 426s ** (umockdev-run:2128): DEBUG: 05:09:06.068: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 426s ** (umockdev-run:2128): DEBUG: 05:09:06.073: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.75AD22/dev/bus/usb/001/001 426s ** (umockdev-run:2128): DEBUG: 05:09:06.073: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 426s ** (umockdev-run:2128): DEBUG: 05:09:06.074: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 426s (process:2132): libfprint-context-DEBUG: 05:09:06.185: Initializing FpContext (libfprint version 1.94.9+tod1) 426s (process:2132): libfprint-tod-DEBUG: 05:09:06.185: 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:2132): libfprint-elanmoc-DEBUG: 05:09:06.188: 131005182415: ../libfprint/drivers/elanmoc/elanmoc.c:1154 426s (process:2132): libfprint-context-DEBUG: 05:09:06.189: No driver found for USB device 1D6B:0002 426s (process:2132): libfprint-device-DEBUG: 05:09:06.189: Device reported probe completion 426s (process:2132): libfprint-device-DEBUG: 05:09:06.189: Completing action FPI_DEVICE_ACTION_PROBE in idle! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.189: Not updating temperature model, device can run continuously! 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.192: [elanmoc] DEV_INIT_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.192: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.193: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.194: [elanmoc] DEV_INIT_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.194: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.194: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.195: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.196: [elanmoc] DEV_INIT_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.196: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.196: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.196: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.197: elanmoc FW Version 8004 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.197: [elanmoc] DEV_INIT_STATES entering state 3 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.197: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.198: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.198: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.199: elanmoc last_read DIM 0x57(87) 0x6B(107) 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.199: [elanmoc] DEV_INIT_STATES entering state 4 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.199: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.199: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.200: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.200: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.200: [elanmoc] DEV_INIT_STATES completed successfully 426s (process:2132): libfprint-device-DEBUG: 05:09:06.200: Device reported open completion 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.200: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-device-DEBUG: 05:09:06.200: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.200: Not updating temperature model, device can run continuously! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.202: Not updating temperature model, device can run continuously! 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.202: [elanmoc] MOC_ENROLL_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.202: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.203: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.203: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.203: [elanmoc] MOC_ENROLL_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.203: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.204: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.204: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.205: ##### Re-Enrollment Case! ##### 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.205: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.205: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.205: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.206: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.207: Device reported enroll progress, reported 1 of 9 have been completed 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.207: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.207: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.207: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.208: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.210: Device reported enroll progress, reported 2 of 9 have been completed 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.210: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.210: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.211: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.212: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.213: Device reported enroll progress, reported 3 of 9 have been completed 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.213: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.213: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.213: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.214: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.215: Device reported enroll progress, reported 4 of 9 have been completed 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.215: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.215: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.216: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.216: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.217: Device reported enroll progress, reported 5 of 9 have been completed 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.217: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.217: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.218: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.218: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.219: Device reported enroll progress, reported 6 of 9 have been completed 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.219: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.219: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.219: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.220: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.220: Device reported enroll progress, reported 7 of 9 have been completed 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.221: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.221: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.221: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.221: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.223: Device reported enroll progress, reported 7 of 9 have been completed 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.223: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.223: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.223: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.223: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.224: Device reported enroll progress, reported 8 of 9 have been completed 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.224: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.224: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.225: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.225: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.226: Device reported enroll progress, reported 8 of 9 have been completed 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.226: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.226: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.227: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.227: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.228: Device reported enroll progress, reported 9 of 9 have been completed 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.228: [elanmoc] MOC_ENROLL_NUM_STATES entering state 3 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.228: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.228: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.229: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.229: elanmoc_commit_cb success 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.229: Enrollment was successful! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.229: Device reported enroll completion 426s (process:2132): libfprint-device-DEBUG: 05:09:06.229: Print for finger FP_FINGER_UNKNOWN enrolled 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.229: [elanmoc] MOC_ENROLL_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.229: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-device-DEBUG: 05:09:06.230: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.230: Not updating temperature model, device can run continuously! 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.230: [elanmoc] MOC_LIST_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.230: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.231: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.231: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.231: [elanmoc] MOC_LIST_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.231: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.232: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.232: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.233: [elanmoc] MOC_LIST_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.233: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.234: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.234: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.235: [elanmoc] MOC_LIST_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.235: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.235: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.236: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.237: [elanmoc] MOC_LIST_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.237: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.237: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.238: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.239: [elanmoc] MOC_LIST_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.239: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.239: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.239: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.240: [elanmoc] MOC_LIST_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.240: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.241: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.241: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.242: [elanmoc] MOC_LIST_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.242: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.242: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.243: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.244: [elanmoc] MOC_LIST_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.244: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.244: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.245: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.246: [elanmoc] MOC_LIST_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.246: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.246: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.247: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.248: [elanmoc] MOC_LIST_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.248: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.248: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.248: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.249: Device reported listing completion 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.249: [elanmoc] MOC_LIST_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.249: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-device-DEBUG: 05:09:06.249: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.249: Not updating temperature model, device can run continuously! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.250: Not updating temperature model, device can run continuously! 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.250: [elanmoc] IDENTIFY_NUM_STATES entering state 0 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.250: elanmoc elan_identify_run_state 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.250: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.250: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.251: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.251: [elanmoc] IDENTIFY_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.251: elanmoc elan_identify_run_state 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.251: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.251: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.252: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.252: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.253: Verify was successful! for user: 0 mesg_code: 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.253: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.254: [elanmoc] IDENTIFY_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.254: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.254: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.255: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 426s (process:2132): libfprint-device-DEBUG: 05:09:06.255: Device reported verify result 426s (process:2132): libfprint-device-DEBUG: 05:09:06.255: Device reported verify completion 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.255: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-device-DEBUG: 05:09:06.255: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.255: Not updating temperature model, device can run continuously! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.256: Not updating temperature model, device can run continuously! 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.256: [elanmoc] IDENTIFY_NUM_STATES entering state 0 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.256: elanmoc elan_identify_run_state 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.256: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.256: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.257: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.257: [elanmoc] IDENTIFY_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.257: elanmoc elan_identify_run_state 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.257: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.257: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.258: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.258: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.259: Verify was successful! for user: 0 mesg_code: 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.259: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.260: [elanmoc] IDENTIFY_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.260: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.260: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.261: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 426s (process:2132): libfprint-device-DEBUG: 05:09:06.261: Device reported identify result 426s (process:2132): libfprint-device-DEBUG: 05:09:06.261: Device reported identify completion 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.261: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-device-DEBUG: 05:09:06.261: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.261: Not updating temperature model, device can run continuously! 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.262: Delete Finger, user_id = FP1-00000000-0-00000000-nobody! 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.262: [elanmoc] DELETE_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.262: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.262: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-device-DEBUG: 05:09:06.263: Device reported deletion completion 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.263: [elanmoc] DELETE_NUM_STATES completed successfully 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.263: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-device-DEBUG: 05:09:06.263: Completing action FPI_DEVICE_ACTION_DELETE in idle! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.263: Not updating temperature model, device can run continuously! 426s (process:2132): libfprint-elanmoc-DEBUG: 05:09:06.263: Elanmoc dev_exit 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.263: [elanmoc] DEV_EXIT_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.264: [elanmoc] FP_CMD_NUM_STATES entering state 0 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.264: [elanmoc] FP_CMD_NUM_STATES entering state 1 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.264: [elanmoc] DEV_EXIT_STATES completed successfully 426s (process:2132): libfprint-device-DEBUG: 05:09:06.265: Device reported close completion 426s (process:2132): libfprint-SSM-DEBUG: 05:09:06.265: [elanmoc] FP_CMD_NUM_STATES completed successfully 426s (process:2132): libfprint-device-DEBUG: 05:09:06.265: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s (process:2132): libfprint-device-DEBUG: 05:09:06.265: Not updating temperature model, device can run continuously! 426s enrolling 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf4a2f548 (FpiDeviceElanmoc at 0x17d3d38)>, 1, None, None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf4a2f548 (FpiDeviceElanmoc at 0x17d3d38)>, 2, None, None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf4a2f548 (FpiDeviceElanmoc at 0x17d3d38)>, 3, None, None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf4a2f548 (FpiDeviceElanmoc at 0x17d3d38)>, 4, None, None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf4a2f548 (FpiDeviceElanmoc at 0x17d3d38)>, 5, None, None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf4a2f548 (FpiDeviceElanmoc at 0x17d3d38)>, 6, None, None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf4a2f548 (FpiDeviceElanmoc at 0x17d3d38)>, 7, None, None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf4a2f548 (FpiDeviceElanmoc at 0x17d3d38)>, 7, 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__.FpiDeviceElanmoc object at 0xf4a2f548 (FpiDeviceElanmoc at 0x17d3d38)>, 8, None, None, None) 426s finger status: 426s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf4a2f548 (FpiDeviceElanmoc at 0x17d3d38)>, 8, 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__.FpiDeviceElanmoc object at 0xf4a2f548 (FpiDeviceElanmoc at 0x17d3d38)>, 9, None, None, None) 426s enroll done 426s listing 426s listing done 426s verifying 426s verify done 426s async identifying 426s indentification_done: 426s deleting 426s delete done 426s ** (umockdev-run:2128): DEBUG: 05:09:06.295: umockdev.vala:154: Removing test bed /tmp/umockdev.75AD22 426s (umockdev-run:2128): GLib-DEBUG: 05:09:06.301: unsetenv() is not thread-safe and should not be used after threads are created 426s PASS: libfprint-2/driver-elanmoc.test 426s Running test: libfprint-2/driver-realtek-5816.test 426s ** (umockdev-run:2140): DEBUG: 05:09:06.414: umockdev.vala:127: Created udev test bed /tmp/umockdev.3ETK22 426s ** (umockdev-run:2140): DEBUG: 05:09:06.414: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-6 426s ** (umockdev-run:2140): DEBUG: 05:09:06.417: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-6 (subsystem usb) 426s ** (umockdev-run:2140): DEBUG: 05:09:06.422: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3ETK22/dev/bus/usb/001/006 426s ** (umockdev-run:2140): DEBUG: 05:09:06.422: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 426s ** (umockdev-run:2140): DEBUG: 05:09:06.423: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 426s ** (umockdev-run:2140): DEBUG: 05:09:06.427: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3ETK22/dev/bus/usb/001/001 426s ** (umockdev-run:2140): DEBUG: 05:09:06.427: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 426s ** (umockdev-run:2140): DEBUG: 05:09:06.428: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 426s (process:2144): libfprint-context-DEBUG: 05:09:06.541: Initializing FpContext (libfprint version 1.94.9+tod1) 426s (process:2144): libfprint-tod-DEBUG: 05:09:06.541: 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:2144): libfprint-context-DEBUG: 05:09:06.544: No driver found for USB device 1D6B:0002 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.544: 131005538593: ../libfprint/drivers/realtek/realtek.c:1224 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.547: Device name: Realtek USB2.0 Finger Print Bridge 426s (process:2144): libfprint-device-DEBUG: 05:09:06.547: Device reported probe completion 426s (process:2144): libfprint-device-DEBUG: 05:09:06.548: Completing action FPI_DEVICE_ACTION_PROBE in idle! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.548: Not updating temperature model, device can run continuously! 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.549: 131005543034: ../libfprint/drivers/realtek/realtek.c:1269 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.550: [realtek] Init entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.550: [realtek] Init entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.550: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.551: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.551: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.552: [realtek] Init entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.552: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.552: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.552: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.553: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.554: [realtek] Init completed successfully 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.554: Init complete! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.554: Device reported open completion 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.554: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-device-DEBUG: 05:09:06.554: Completing action FPI_DEVICE_ACTION_OPEN in idle! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.554: Not updating temperature model, device can run continuously! 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.554: 131005547893: ../libfprint/drivers/realtek/realtek.c:1332 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.554: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.554: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.554: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.555: Successfully cleared storage 426s (process:2144): libfprint-device-DEBUG: 05:09:06.555: Device reported deletion completion 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.555: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-device-DEBUG: 05:09:06.555: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.555: Not updating temperature model, device can run continuously! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.556: Not updating temperature model, device can run continuously! 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.556: 131005549963: ../libfprint/drivers/realtek/realtek.c:1201 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.556: [realtek] Enroll entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.556: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.556: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.557: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.558: [realtek] Enroll entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.558: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.558: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.558: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.558: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.559: [realtek] Enroll entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.559: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.559: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.559: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.559: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.559: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.560: [realtek] Enroll entering state 3 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.560: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.560: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.561: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.561: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.562: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.562: [realtek] Enroll entering state 4 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.562: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.562: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.562: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.563: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.563: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2144): libfprint-device-DEBUG: 05:09:06.563: Device reported enroll progress, reported 1 of 8 have been completed 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.564: [realtek] Enroll entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.564: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.564: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.564: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.566: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.566: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.567: [realtek] Enroll entering state 3 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.567: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.567: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.567: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.568: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.568: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.568: [realtek] Enroll entering state 4 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.568: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.569: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.569: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.569: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.570: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2144): libfprint-device-DEBUG: 05:09:06.570: Device reported enroll progress, reported 2 of 8 have been completed 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.570: [realtek] Enroll entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.570: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.570: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.570: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.571: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.571: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.571: [realtek] Enroll entering state 3 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.571: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.572: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.572: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.572: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.573: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.573: [realtek] Enroll entering state 4 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.573: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.573: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.573: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.574: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.575: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2144): libfprint-device-DEBUG: 05:09:06.575: Device reported enroll progress, reported 3 of 8 have been completed 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.575: [realtek] Enroll entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.575: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.575: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.575: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.575: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.575: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.576: [realtek] Enroll entering state 3 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.576: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.576: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.576: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.577: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.577: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.577: [realtek] Enroll entering state 4 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.577: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.578: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.578: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.579: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.579: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2144): libfprint-device-DEBUG: 05:09:06.579: Device reported enroll progress, reported 4 of 8 have been completed 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.579: [realtek] Enroll entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.579: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.579: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.579: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.580: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.580: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.580: [realtek] Enroll entering state 3 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.580: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.581: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.581: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.581: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.582: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.582: [realtek] Enroll entering state 4 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.582: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.582: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.582: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.583: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.584: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2144): libfprint-device-DEBUG: 05:09:06.584: Device reported enroll progress, reported 5 of 8 have been completed 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.584: [realtek] Enroll entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.584: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.584: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.584: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.584: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.584: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.585: [realtek] Enroll entering state 3 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.585: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.585: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.585: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.586: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.586: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.586: [realtek] Enroll entering state 4 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.586: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.586: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.587: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.587: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.588: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2144): libfprint-device-DEBUG: 05:09:06.588: Device reported enroll progress, reported 6 of 8 have been completed 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.588: [realtek] Enroll entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.588: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.588: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.588: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.588: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.588: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.589: [realtek] Enroll entering state 3 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.589: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.589: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.589: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.590: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.590: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.590: [realtek] Enroll entering state 4 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.590: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.591: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.591: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.591: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.592: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2144): libfprint-device-DEBUG: 05:09:06.592: Device reported enroll progress, reported 7 of 8 have been completed 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.592: [realtek] Enroll entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.592: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.592: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.592: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.592: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.592: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.593: [realtek] Enroll entering state 3 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.593: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.593: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.593: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.594: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.594: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.594: [realtek] Enroll entering state 4 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.594: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.595: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.595: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.596: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.596: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2144): libfprint-device-DEBUG: 05:09:06.596: Device reported enroll progress, reported 8 of 8 have been completed 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.596: [realtek] Enroll entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.596: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.596: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.596: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.597: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.597: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.597: [realtek] Enroll entering state 3 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.597: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.597: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.598: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.598: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.599: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.599: [realtek] Enroll entering state 4 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.599: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.599: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.599: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.600: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.600: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.600: [realtek] Enroll entering state 5 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.600: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.601: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.601: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.601: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.602: [realtek] Enroll entering state 6 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.602: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.602: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.602: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.602: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.603: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.604: [realtek] Enroll completed successfully 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.604: Enrollment complete! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.604: Device reported enroll completion 426s (process:2144): libfprint-device-DEBUG: 05:09:06.604: Print for finger FP_FINGER_UNKNOWN enrolled 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.604: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-device-DEBUG: 05:09:06.604: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.604: Not updating temperature model, device can run continuously! 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.604: 131005597944: ../libfprint/drivers/realtek/realtek.c:1344 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.604: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.604: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.605: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.605: Query templates complete! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.605: Device reported listing completion 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.605: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-device-DEBUG: 05:09:06.605: Completing action FPI_DEVICE_ACTION_LIST in idle! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.605: Not updating temperature model, device can run continuously! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.606: Not updating temperature model, device can run continuously! 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.606: 131005599859: ../libfprint/drivers/realtek/realtek.c:1177 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.606: [realtek] Verify & Identify entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.606: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.606: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.607: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.607: [realtek] Verify & Identify entering state 1 426s (process:2144): libfprint-device-DEBUG: 05:09:06.607: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.607: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.607: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.608: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.608: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.608: [realtek] Verify & Identify entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.608: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.609: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.609: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.610: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.610: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.610: [realtek] Verify & Identify entering state 3 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.610: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.610: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.611: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.611: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.612: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.612: [realtek] Verify & Identify entering state 4 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.612: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.612: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.612: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.613: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.613: Device reported verify result 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.613: [realtek] Verify & Identify entering state 5 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.614: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.614: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.614: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.614: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.615: [realtek] Verify & Identify completed successfully 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.615: Verify complete! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.615: Device reported verify completion 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.615: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-device-DEBUG: 05:09:06.615: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.615: Not updating temperature model, device can run continuously! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.615: Not updating temperature model, device can run continuously! 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.615: 131005609416: ../libfprint/drivers/realtek/realtek.c:1177 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.615: [realtek] Verify & Identify entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.615: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.616: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.616: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.617: [realtek] Verify & Identify entering state 1 426s (process:2144): libfprint-device-DEBUG: 05:09:06.617: Device reported finger status change: FP_FINGER_STATUS_NEEDED 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.617: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.617: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.618: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.618: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.618: [realtek] Verify & Identify entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.618: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.618: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.619: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.619: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.620: Device reported finger status change: FP_FINGER_STATUS_PRESENT 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.620: [realtek] Verify & Identify entering state 3 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.620: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.620: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.620: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.621: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.622: Device reported finger status change: FP_FINGER_STATUS_NONE 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.622: [realtek] Verify & Identify entering state 4 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.622: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.622: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.622: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.623: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-device-DEBUG: 05:09:06.623: Device reported identify result 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.623: [realtek] Verify & Identify completed successfully 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.623: Verify complete! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.623: Device reported identify completion 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.623: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-device-DEBUG: 05:09:06.623: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.623: Not updating temperature model, device can run continuously! 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.624: 131005618213: ../libfprint/drivers/realtek/realtek.c:1313 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.624: [realtek] Delete print entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.624: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.625: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.625: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.626: [realtek] Delete print entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.626: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.626: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.626: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.626: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.627: [realtek] Delete print completed successfully 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.627: Delete print complete! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.627: Device reported deletion completion 426s (process:2144): libfprint-SSM-DEBUG: 05:09:06.627: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 426s (process:2144): libfprint-device-DEBUG: 05:09:06.627: Completing action FPI_DEVICE_ACTION_DELETE in idle! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.627: Not updating temperature model, device can run continuously! 426s (process:2144): libfprint-realtek-DEBUG: 05:09:06.627: 131005621273: ../libfprint/drivers/realtek/realtek.c:1301 426s (process:2144): libfprint-device-DEBUG: 05:09:06.627: Device reported close completion 426s (process:2144): libfprint-device-DEBUG: 05:09:06.627: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 426s (process:2144): libfprint-device-DEBUG: 05:09:06.627: Not updating temperature model, device can run continuously! 426s enrolling 426s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf61c0688 (FpiDeviceRealtek at 0x1b88720)>, 1, None, None, None) 426s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf61c0688 (FpiDeviceRealtek at 0x1b88720)>, 2, None, None, None) 426s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf61c0688 (FpiDeviceRealtek at 0x1b88720)>, 3, None, None, None) 426s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf61c0688 (FpiDeviceRealtek at 0x1b88720)>, 4, None, None, None) 426s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf61c0688 (FpiDeviceRealtek at 0x1b88720)>, 5, None, None, None) 426s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf61c0688 (FpiDeviceRealtek at 0x1b88720)>, 6, None, None, None) 426s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf61c0688 (FpiDeviceRealtek at 0x1b88720)>, 7, None, None, None) 426s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf61c0688 (FpiDeviceRealtek at 0x1b88720)>, 8, None, None, None) 426s enroll done 426s listing 426s listing done 426s verifying 426s verify done 426s async identifying 426s indentification_done: 426s deleting 426s delete done 426s ** (umockdev-run:2140): DEBUG: 05:09:06.654: umockdev.vala:154: Removing test bed /tmp/umockdev.3ETK22 426s (umockdev-run:2140): GLib-DEBUG: 05:09:06.661: unsetenv() is not thread-safe and should not be used after threads are created 426s PASS: libfprint-2/driver-realtek-5816.test 426s Running test: libfprint-2/fpi-ssm.test 426s TAP version 14 426s # random seed: R02Sa3f09a0b1d22772a8db675647d09b117 426s 1..42 426s # Start of ssm tests 426s ok 1 /ssm/new 426s ok 2 /ssm/set_data 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 426s ok 3 /ssm/start 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 426s ok 4 /ssm/next 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 426s ok 5 /ssm/jump_to_state 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 426s ok 6 /ssm/mark_completed 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 426s # 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. 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 426s ok 7 /ssm/mark_failed 426s # Start of new tests 426s ok 8 /ssm/new/full 426s ok 9 /ssm/new/no_handler 426s ok 10 /ssm/new/wrong_states 426s # End of new tests 426s # Start of set_data tests 426s ok 11 /ssm/set_data/cleanup 426s # End of set_data tests 426s # Start of start tests 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully 426s ok 12 /ssm/start/single 426s # End of start tests 426s # Start of next tests 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 426s ok 13 /ssm/next/complete 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 426s ok 14 /ssm/next/not_started 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 426s ok 15 /ssm/next/with_delayed 426s # End of next tests 426s # Start of jump_to_state tests 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 426s ok 16 /ssm/jump_to_state/not_started 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 426s ok 17 /ssm/jump_to_state/with_delayed 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 426s ok 18 /ssm/jump_to_state/last 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 426s ok 19 /ssm/jump_to_state/wrong 426s # End of jump_to_state tests 426s # Start of mark_completed tests 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 426s ok 20 /ssm/mark_completed/not_started 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 426s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 427s ok 21 /ssm/mark_completed/with_delayed 427s # End of mark_completed tests 427s # Start of mark_failed tests 427s # 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. 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 427s ok 22 /ssm/mark_failed/not_started 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # 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. 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 427s ok 23 /ssm/mark_failed/with_delayed 427s # End of mark_failed tests 427s # Start of delayed tests 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 427s ok 24 /ssm/delayed/next 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 427s ok 25 /ssm/delayed/jump_to_state 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 427s ok 26 /ssm/delayed/mark_completed 427s # Start of next tests 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 427s ok 27 /ssm/delayed/next/cancel 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 427s ok 28 /ssm/delayed/next/not_started 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 427s ok 29 /ssm/delayed/next/complete 427s # End of next tests 427s # Start of jump_to_state tests 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 427s ok 30 /ssm/delayed/jump_to_state/cancel 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 427s ok 31 /ssm/delayed/jump_to_state/not_started 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 427s ok 32 /ssm/delayed/jump_to_state/last 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 427s ok 33 /ssm/delayed/jump_to_state/wrong 427s # End of jump_to_state tests 427s # Start of mark_completed tests 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 427s ok 34 /ssm/delayed/mark_completed/cancel 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 427s ok 35 /ssm/delayed/mark_completed/not_started 427s # End of mark_completed tests 427s # Start of cancel tests 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 427s ok 36 /ssm/delayed/cancel/error 427s # End of cancel tests 427s # End of delayed tests 427s # Start of subssm tests 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 427s ok 37 /ssm/subssm/start 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 427s # 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. 427s # 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. 427s # 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. 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 427s ok 38 /ssm/subssm/mark_failed 427s # Start of start tests 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 427s ok 39 /ssm/subssm/start/with_started 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 427s ok 40 /ssm/subssm/start/with_delayed 427s # End of start tests 427s # End of subssm tests 427s # Start of cleanup tests 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 427s ok 41 /ssm/cleanup/complete 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 427s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 427s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 427s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 427s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: non-cleanup 427s ok 42 /ssm/cleanup/fail 427s # End of cleanup tests 427s # End of ssm tests 427s PASS: libfprint-2/fpi-ssm.test 427s Running test: libfprint-2/driver-elan-cobo.test 427s ** (umockdev-run:2154): DEBUG: 05:09:07.777: umockdev.vala:127: Created udev test bed /tmp/umockdev.1A7212 427s ** (umockdev-run:2154): DEBUG: 05:09:07.777: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 427s ** (umockdev-run:2154): DEBUG: 05:09:07.779: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 427s ** (umockdev-run:2154): DEBUG: 05:09:07.782: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.1A7212/dev/bus/usb/001/045 427s ** (umockdev-run:2154): DEBUG: 05:09:07.783: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 427s ** (umockdev-run:2154): DEBUG: 05:09:07.784: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 427s ** (umockdev-run:2154): DEBUG: 05:09:07.788: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.1A7212/dev/bus/usb/001/001 427s ** (umockdev-run:2154): DEBUG: 05:09:07.788: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 427s ** (umockdev-run:2154): DEBUG: 05:09:07.789: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 427s (process:2158): libfprint-context-DEBUG: 05:09:07.898: Initializing FpContext (libfprint version 1.94.9+tod1) 427s (process:2158): libfprint-tod-DEBUG: 05:09:07.898: 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:2158): libfprint-context-DEBUG: 05:09:07.901: No driver found for USB device 1D6B:0002 427s (process:2158): libfprint-device-DEBUG: 05:09:07.901: Device reported probe completion 427s (process:2158): libfprint-device-DEBUG: 05:09:07.901: Completing action FPI_DEVICE_ACTION_PROBE in idle! 427s (process:2158): libfprint-device-DEBUG: 05:09:07.901: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.903: 131006896950: ../libfprint/drivers/elan.c:908 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.903: Image device open completed 427s (process:2158): libfprint-device-DEBUG: 05:09:07.903: Device reported open completion 427s (process:2158): libfprint-device-DEBUG: 05:09:07.903: Completing action FPI_DEVICE_ACTION_OPEN in idle! 427s (process:2158): libfprint-device-DEBUG: 05:09:07.903: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 427s (process:2158): libfprint-device-DEBUG: 05:09:07.904: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.904: Activating image device 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.904: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.904: 131006897959: ../libfprint/drivers/elan.c:960 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.904: 131006897970: ../libfprint/drivers/elan.c:951 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.904: 131006897974: ../libfprint/drivers/elan.c:892 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.904: 131006897978: ../libfprint/drivers/elan.c:100 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.904: [elan] ACTIVATE_NUM_STATES entering state 0 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.904: 131006897996: ../libfprint/drivers/elan.c:820 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.904: 131006898605: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.904: 131006898637: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.904: 131006898643: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.905: 131006899231: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.905: 131006899253: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.905: [elan] ACTIVATE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.905: 131006899267: ../libfprint/drivers/elan.c:820 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.905: FW ver 0x0140 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.905: [elan] ACTIVATE_NUM_STATES entering state 2 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.905: 131006899279: ../libfprint/drivers/elan.c:820 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006899744: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006899763: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006899768: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006900243: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006900263: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.906: [elan] ACTIVATE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006900274: ../libfprint/drivers/elan.c:820 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: sensor dimensions, WxH: 144x64 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.906: [elan] ACTIVATE_NUM_STATES entering state 4 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006900285: ../libfprint/drivers/elan.c:820 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006900293: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.906: [elan] ACTIVATE_NUM_STATES completed successfully 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006900319: ../libfprint/drivers/elan.c:881 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.906: Image device activation completed 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.906: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006900342: ../libfprint/drivers/elan.c:960 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.906: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006900351: ../libfprint/drivers/elan.c:960 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006900354: ../libfprint/drivers/elan.c:792 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006900357: ../libfprint/drivers/elan.c:100 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.906: [elan] CALIBRATE_NUM_STATES entering state 0 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.906: 131006900366: ../libfprint/drivers/elan.c:691 427s (process:2158): libfprint-device-DEBUG: 05:09:07.906: Device reported finger status change: FP_FINGER_STATUS_NEEDED 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.907: 131006900763: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.907: 131006900776: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.907: 131006900782: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.907: 131006901405: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.907: 131006901478: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.907: [elan] CALIBRATE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.907: 131006901490: ../libfprint/drivers/elan.c:691 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.907: 131006901494: ../libfprint/drivers/elan.c:156 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.907: 131006901497: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.907: [elan] CALIBRATE_NUM_STATES entering state 2 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.907: 131006901518: ../libfprint/drivers/elan.c:691 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.908: 131006901951: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.908: 131006901965: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.908: 131006901971: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.908: 131006902502: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.908: 131006902524: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.908: [elan] CALIBRATE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.908: 131006902534: ../libfprint/drivers/elan.c:691 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.908: 131006902538: ../libfprint/drivers/elan.c:634 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.908: calibration mean: 8248, bg mean: 7978, delta: 270 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.908: [elan] CALIBRATE_NUM_STATES completed successfully 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.908: 131006902559: ../libfprint/drivers/elan.c:776 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.908: 131006902563: ../libfprint/drivers/elan.c:620 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.908: 131006902566: ../libfprint/drivers/elan.c:100 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.908: [elan] CAPTURE_NUM_STATES entering state 0 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.909: 131006902983: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.909: 131006903045: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.909: 131006903053: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.909: skipping read, not expecting anything 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.909: 131006903060: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.909: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.909: 131006903532: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.909: 131006903550: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.909: 131006903556: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.910: 131006904031: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.910: 131006904049: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.910: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-device-DEBUG: 05:09:07.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.910: Image device reported finger status: on 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.910: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.910: 131006904092: ../libfprint/drivers/elan.c:960 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.910: 131006904553: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.910: 131006904572: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.910: 131006904578: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.911: 131006905160: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.911: 131006905186: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.911: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.911: 131006905199: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.911: 131006905213: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.911: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.911: 131006905694: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.911: 131006905712: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.911: 131006905719: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.912: 131006906235: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.912: 131006906258: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.912: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.912: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.913: 131006906776: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.913: 131006906794: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.913: 131006906801: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.913: 131006907428: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.913: 131006907455: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.913: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.913: 131006907466: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.913: 131006907479: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.913: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.914: 131006907949: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.914: 131006907967: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.914: 131006907974: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.914: 131006908536: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.914: 131006908558: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.914: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.914: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.915: 131006909041: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.915: 131006909061: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.915: 131006909067: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.915: 131006909664: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.915: 131006909685: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.915: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.915: 131006909697: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.916: 131006909726: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.916: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.916: 131006910200: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.916: 131006910223: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.916: 131006910230: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.917: 131006910753: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.917: 131006910771: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.917: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.917: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.917: 131006911274: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.917: 131006911296: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.917: 131006911316: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.918: 131006911893: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.918: 131006911914: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.918: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.918: 131006911927: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.918: 131006911939: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.918: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.918: 131006912457: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.918: 131006912481: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.918: 131006912488: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.919: 131006913020: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.919: 131006913041: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.919: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.919: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.919: 131006913543: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.919: 131006913566: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.919: 131006913572: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.920: 131006914162: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.920: 131006914187: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.920: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.920: 131006914199: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.920: 131006914211: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.920: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.920: 131006914689: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.920: 131006914709: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.920: 131006914715: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.921: 131006915221: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.921: 131006915245: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.921: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.921: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.922: 131006915750: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.922: 131006915769: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.922: 131006915775: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.922: 131006916369: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.922: 131006916394: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.922: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.922: 131006916406: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.922: 131006916419: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.922: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.923: 131006916882: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.923: 131006916899: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.923: 131006916905: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.923: 131006917452: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.923: 131006917476: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.923: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.923: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.924: 131006917955: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.924: 131006917972: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.924: 131006917978: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.924: 131006918582: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.924: 131006918608: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.924: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.924: 131006918620: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.924: 131006918632: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.924: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.925: 131006919119: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.925: 131006919140: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.925: 131006919147: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.925: 131006919679: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.925: 131006919699: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.925: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.925: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.926: 131006920184: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.926: 131006920206: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.926: 131006920213: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.927: 131006920804: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.927: 131006920825: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.927: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.927: 131006920836: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.927: 131006920849: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.927: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.927: 131006921333: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.927: 131006921359: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.927: 131006921367: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.928: 131006921884: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.928: 131006921902: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.928: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.928: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.928: 131006922443: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.928: 131006922464: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.928: 131006922470: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.929: 131006923052: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.929: 131006923077: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.929: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.929: 131006923088: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.929: 131006923102: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.929: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.929: 131006923590: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.929: 131006923610: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.929: 131006923617: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.930: 131006924135: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.930: 131006924155: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.930: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.930: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.930: 131006924640: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.930: 131006924657: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.930: 131006924663: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.931: 131006925220: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.931: 131006925242: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.931: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.931: 131006925253: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.931: 131006925265: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.931: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.931: 131006925714: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.932: 131006925731: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.932: 131006925736: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.932: 131006926221: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.932: 131006926241: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.932: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.932: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.932: 131006926716: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.933: 131006926735: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.933: 131006926741: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.933: 131006927279: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.933: 131006927325: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.933: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.933: 131006927336: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.933: 131006927348: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.933: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.934: 131006927770: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.934: 131006927789: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.934: 131006927794: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.934: 131006928284: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.934: 131006928319: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.934: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.934: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.935: 131006928804: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.935: 131006928821: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.935: 131006928827: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.935: 131006929422: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.935: 131006929445: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.935: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.935: 131006929457: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.935: 131006929468: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.935: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.936: 131006929938: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.936: 131006929954: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.936: 131006929958: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.936: 131006930494: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.936: 131006930514: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.936: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.936: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.937: 131006930956: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.937: 131006930972: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.937: 131006930978: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.937: 131006931589: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.937: 131006931612: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.937: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.937: 131006931622: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.937: 131006931644: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.937: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.938: 131006932452: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.938: 131006932472: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.938: 131006932478: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.939: 131006932986: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.939: 131006933014: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.939: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.939: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.939: 131006933501: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.939: 131006933518: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.939: 131006933523: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.940: 131006934066: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.940: 131006934089: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.940: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.940: 131006934099: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.940: 131006934110: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.940: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.940: 131006934551: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.940: 131006934569: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.940: 131006934575: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.941: 131006935048: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.941: 131006935071: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.941: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.941: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.941: 131006935545: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.941: 131006935564: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.941: 131006935569: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.942: 131006936112: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.942: 131006936137: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.942: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.942: 131006936149: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.942: 131006936159: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.942: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.942: 131006936679: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.942: 131006936698: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.942: 131006936704: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.943: 131006937202: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.943: 131006937223: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.943: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-image_device-DEBUG: 05:09:07.943: Image device reported finger status: on 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.943: 131006937682: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.943: 131006937700: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.943: 131006937706: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.944: 131006938232: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.944: 131006938253: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.944: [elan] CAPTURE_NUM_STATES entering state 3 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.944: 131006938263: ../libfprint/drivers/elan.c:203 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.944: 131006938275: ../libfprint/drivers/elan.c:118 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.944: [elan] CAPTURE_NUM_STATES entering state 1 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.945: 131006938742: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.945: 131006938759: ../libfprint/drivers/elan.c:366 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.945: 131006938764: ../libfprint/drivers/elan.c:379 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.945: 131006939228: ../libfprint/drivers/elan.c:346 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.945: 131006939250: ../libfprint/drivers/elan.c:335 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.945: [elan] CAPTURE_NUM_STATES entering state 2 427s (process:2158): libfprint-SSM-DEBUG: 05:09:07.945: [elan] CAPTURE_NUM_STATES completed successfully 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.945: 131006939276: ../libfprint/drivers/elan.c:586 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.945: 131006939279: ../libfprint/drivers/elan.c:315 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.945: 131006939286: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.946: 131006940157: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.947: 131006940998: ../libfprint/drivers/elan.c:272 427s Executing: libfprint-2/driver-elan-cobo.test 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.948: 131006941882: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.949: 131006942751: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.949: 131006943602: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.950: 131006944443: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.951: 131006945274: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.952: 131006946111: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.953: 131006946954: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.954: 131006947803: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.954: 131006948640: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.955: 131006949479: ../libfprint/drivers/elan.c:272 427s (process:2158): libfprint-elan-DEBUG: 05:09:07.956: 131006950337: ../libfprint/drivers/elan.c:272 428s (process:2158): libfprint-assembling-DEBUG: 05:09:08.212: calc delta completed in 0.254716 secs 428s (process:2158): libfprint-assembling-DEBUG: 05:09:08.466: calc delta completed in 0.254225 secs 428s (process:2158): libfprint-assembling-DEBUG: 05:09:08.466: errors: 133465 rev: 143589 428s (process:2158): libfprint-assembling-DEBUG: 05:09:08.722: calc delta completed in 0.255839 secs 428s (process:2158): libfprint-assembling-DEBUG: 05:09:08.722: height is 225 428s (process:2158): libfprint-image_device-DEBUG: 05:09:08.722: Image device captured an image 428s (process:2158): libfprint-image_device-DEBUG: 05:09:08.724: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.724: 131007718133: ../libfprint/drivers/elan.c:960 428s (process:2158): libfprint-device-DEBUG: 05:09:08.724: Device reported finger status change: FP_FINGER_STATUS_PRESENT 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.724: 131007718157: ../libfprint/drivers/elan.c:507 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.724: 131007718164: ../libfprint/drivers/elan.c:100 428s (process:2158): libfprint-SSM-DEBUG: 05:09:08.724: [elan] STOP_CAPTURE_NUM_STATES entering state 0 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.724: 131007718181: ../libfprint/drivers/elan.c:466 428s (process:2158): libfprint-device-DEBUG: 05:09:08.724: Updated temperature model after 0.82 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.725: 131007718759: ../libfprint/drivers/elan.c:346 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.725: 131007718778: ../libfprint/drivers/elan.c:366 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.725: 131007718783: ../libfprint/drivers/elan.c:379 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.725: skipping read, not expecting anything 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.725: 131007718790: ../libfprint/drivers/elan.c:335 428s (process:2158): libfprint-SSM-DEBUG: 05:09:08.725: [elan] STOP_CAPTURE_NUM_STATES completed successfully 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.725: 131007718798: ../libfprint/drivers/elan.c:483 428s (process:2158): libfprint-device-DEBUG: 05:09:08.725: Device reported finger status change: FP_FINGER_STATUS_NONE 428s (process:2158): libfprint-image_device-DEBUG: 05:09:08.725: Image device reported finger status: off 428s (process:2158): libfprint-image_device-DEBUG: 05:09:08.725: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.725: 131007718821: ../libfprint/drivers/elan.c:960 428s (process:2158): libfprint-image_device-DEBUG: 05:09:08.725: Deactivating image device 428s (process:2158): libfprint-image_device-DEBUG: 05:09:08.725: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.725: 131007718833: ../libfprint/drivers/elan.c:960 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.725: 131007718837: ../libfprint/drivers/elan.c:975 428s (process:2158): libfprint-image_device-DEBUG: 05:09:08.725: Image device deactivation completed 428s (process:2158): libfprint-image_device-DEBUG: 05:09:08.725: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.725: 131007718853: ../libfprint/drivers/elan.c:960 428s (process:2158): libfprint-image-DEBUG: 05:09:08.744: Minutiae scan completed in 0.020224 secs 428s (process:2158): libfprint-device-DEBUG: 05:09:08.744: Device reported capture completion 428s (process:2158): libfprint-device-DEBUG: 05:09:08.745: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 428s (process:2158): libfprint-device-DEBUG: 05:09:08.745: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.745: 131007738890: ../libfprint/drivers/elan.c:939 428s (process:2158): libfprint-elan-DEBUG: 05:09:08.745: 131007738910: ../libfprint/drivers/elan.c:100 428s (process:2158): libfprint-image_device-DEBUG: 05:09:08.745: Image device close completed 428s (process:2158): libfprint-device-DEBUG: 05:09:08.745: Device reported close completion 428s (process:2158): libfprint-device-DEBUG: 05:09:08.745: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 428s (process:2158): libfprint-device-DEBUG: 05:09:08.745: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 428s ** (umockdev-run:2154): DEBUG: 05:09:08.859: umockdev.vala:154: Removing test bed /tmp/umockdev.1A7212 428s (umockdev-run:2154): GLib-DEBUG: 05:09:08.865: unsetenv() is not thread-safe and should not be used after threads are created 428s Comparing PNGs /tmp/libfprint-umockdev-test-o0e7zb8_/capture.png and /usr/share/installed-tests/libfprint-2/elan-cobo/capture.png 428s PASS: libfprint-2/driver-elan-cobo.test 428s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 428s TAP version 14 428s # random seed: R02S1c4c922065864dda45b86226bdaa6f63 428s 1..4 428s # Start of context tests 428s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 428s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 428s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf28b1a45, GType is 191495416 428s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 428s ok 1 /context/new 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.9+tod1) 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 # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 428s ok 2 /context/no-devices 428s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 428s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 428s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf28b1a45, GType is 191495416 428s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 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_FAKE_DEVICE, yes 428s # libfprint-context-DEBUG: created 428s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 428s # 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 # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 428s # 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.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 428s # 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.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 428s ok 3 /context/has-virtual-device 428s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 428s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 428s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf28b1a45, GType is 191495416 428s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 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_FAKE_DEVICE, yes 428s # libfprint-context-DEBUG: created 428s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 428s # 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 ok 4 /context/enumerates-new-devices 428s # End of context tests 428s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 428s Running test: libfprint-2/driver-aes3500.test 429s ** (umockdev-run:2179): DEBUG: 05:09:08.972: umockdev.vala:127: Created udev test bed /tmp/umockdev.3R9912 429s ** (umockdev-run:2179): DEBUG: 05:09:08.972: 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 429s ** (umockdev-run:2179): DEBUG: 05:09:08.976: 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) 429s ** (umockdev-run:2179): DEBUG: 05:09:08.979: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3R9912/dev/bus/usb/003/004 429s ** (umockdev-run:2179): DEBUG: 05:09:08.979: 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 429s ** (umockdev-run:2179): DEBUG: 05:09:08.983: 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) 429s ** (umockdev-run:2179): DEBUG: 05:09:08.987: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3R9912/dev/bus/usb/003/003 429s ** (umockdev-run:2179): DEBUG: 05:09:08.987: 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 429s ** (umockdev-run:2179): DEBUG: 05:09:08.990: 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) 429s ** (umockdev-run:2179): DEBUG: 05:09:08.994: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3R9912/dev/bus/usb/003/002 429s ** (umockdev-run:2179): DEBUG: 05:09:08.994: 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 429s ** (umockdev-run:2179): DEBUG: 05:09:08.997: 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) 429s ** (umockdev-run:2179): DEBUG: 05:09:09.001: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3R9912/dev/bus/usb/003/001 429s ** (umockdev-run:2179): DEBUG: 05:09:09.002: 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 429s ** (umockdev-run:2179): DEBUG: 05:09:09.003: 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) 429s ** (umockdev-run:2179): DEBUG: 05:09:09.007: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 429s ** (umockdev-run:2179): DEBUG: 05:09:09.008: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 (subsystem pci) 429s ** (umockdev-run:2179): DEBUG: 05:09:09.011: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 429s ** (umockdev-run:2179): DEBUG: 05:09:09.012: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 (subsystem pci) 429s ** (umockdev-run:2179): DEBUG: 05:09:09.015: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0 429s ** (umockdev-run:2179): DEBUG: 05:09:09.015: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0 (subsystem pci) 429s (umockdev-run:2179): GLib-GIO-DEBUG: 05:09:09.018: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 429s (process:2183): libfprint-context-DEBUG: 05:09:09.131: Initializing FpContext (libfprint version 1.94.9+tod1) 429s (process:2183): libfprint-tod-DEBUG: 05:09:09.131: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 429s (process:2183): libfprint-context-DEBUG: 05:09:09.136: No driver found for USB device 2230:0006 429s (process:2183): libfprint-context-DEBUG: 05:09:09.136: No driver found for USB device 2230:0006 429s (process:2183): libfprint-context-DEBUG: 05:09:09.136: No driver found for USB device 1D6B:0002 429s (process:2183): libfprint-device-DEBUG: 05:09:09.137: Device reported probe completion 429s (process:2183): libfprint-device-DEBUG: 05:09:09.137: Completing action FPI_DEVICE_ACTION_PROBE in idle! 429s (process:2183): libfprint-device-DEBUG: 05:09:09.137: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.139: Image device open completed 429s (process:2183): libfprint-device-DEBUG: 05:09:09.139: Device reported open completion 429s (process:2183): libfprint-device-DEBUG: 05:09:09.139: Completing action FPI_DEVICE_ACTION_OPEN in idle! 429s (process:2183): libfprint-device-DEBUG: 05:09:09.139: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 429s (process:2183): libfprint-device-DEBUG: 05:09:09.139: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.139: Activating image device 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.139: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 429s (process:2183): libfprint-aeslib-DEBUG: 05:09:09.139: write 50 regs 429s (process:2183): libfprint-aeslib-DEBUG: 05:09:09.144: all registers written 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.144: Image device activation completed 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.144: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.144: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 429s (process:2183): libfprint-aeslib-DEBUG: 05:09:09.144: write 6 regs 429s (process:2183): libfprint-device-DEBUG: 05:09:09.145: Device reported finger status change: FP_FINGER_STATUS_NEEDED 429s (process:2183): libfprint-aeslib-DEBUG: 05:09:09.146: all registers written 429s (process:2183): libfprint-device-DEBUG: 05:09:09.146: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.146: Image device reported finger status: on 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.146: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 429s (process:2183): libfprint-aes3k-DEBUG: 05:09:09.146: frame header byte e0 429s (process:2183): libfprint-aes3k-DEBUG: 05:09:09.146: frame header byte e1 429s (process:2183): libfprint-aes3k-DEBUG: 05:09:09.146: frame header byte e2 429s (process:2183): libfprint-aes3k-DEBUG: 05:09:09.146: frame header byte e3 429s (process:2183): libfprint-aes3k-DEBUG: 05:09:09.146: frame header byte e4 429s (process:2183): libfprint-aes3k-DEBUG: 05:09:09.146: frame header byte e5 429s (process:2183): libfprint-aes3k-DEBUG: 05:09:09.146: frame header byte e6 429s (process:2183): libfprint-aes3k-DEBUG: 05:09:09.146: frame header byte e7 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.147: Image device captured an image 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.148: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 429s (process:2183): libfprint-device-DEBUG: 05:09:09.148: Device reported finger status change: FP_FINGER_STATUS_PRESENT 429s (process:2183): libfprint-device-DEBUG: 05:09:09.148: Device reported finger status change: FP_FINGER_STATUS_NONE 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.148: Image device reported finger status: off 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.148: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.148: Deactivating image device 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.148: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.148: Image device deactivation completed 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.149: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 429s (process:2183): libfprint-image-DEBUG: 05:09:09.172: Minutiae scan completed in 0.023584 secs 429s (process:2183): libfprint-device-DEBUG: 05:09:09.172: Device reported capture completion 429s (process:2183): libfprint-device-DEBUG: 05:09:09.172: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 429s (process:2183): libfprint-device-DEBUG: 05:09:09.172: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 429s (process:2183): libfprint-image_device-DEBUG: 05:09:09.173: Image device close completed 429s (process:2183): libfprint-device-DEBUG: 05:09:09.173: Device reported close completion 429s (process:2183): libfprint-device-DEBUG: 05:09:09.173: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 429s (process:2183): libfprint-device-DEBUG: 05:09:09.173: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 429s ** (umockdev-run:2179): DEBUG: 05:09:09.304: umockdev.vala:154: Removing test bed /tmp/umockdev.3R9912 429s (umockdev-run:2179): GLib-DEBUG: 05:09:09.320: unsetenv() is not thread-safe and should not be used after threads are created 429s Comparing PNGs /tmp/libfprint-umockdev-test-4bhvoq9a/capture.png and /usr/share/installed-tests/libfprint-2/aes3500/capture.png 429s PASS: libfprint-2/driver-aes3500.test 429s Running test: libfprint-2/driver-vfs7552.test 429s ** (umockdev-run:2192): DEBUG: 05:09:09.405: umockdev.vala:127: Created udev test bed /tmp/umockdev.7MEL22 429s ** (umockdev-run:2192): DEBUG: 05:09:09.405: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 429s ** (umockdev-run:2192): DEBUG: 05:09:09.407: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 429s ** (umockdev-run:2192): DEBUG: 05:09:09.411: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7MEL22/dev/bus/usb/001/003 429s ** (umockdev-run:2192): DEBUG: 05:09:09.411: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 429s ** (umockdev-run:2192): DEBUG: 05:09:09.412: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 429s ** (umockdev-run:2192): DEBUG: 05:09:09.416: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7MEL22/dev/bus/usb/001/001 429s ** (umockdev-run:2192): DEBUG: 05:09:09.417: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 429s ** (umockdev-run:2192): DEBUG: 05:09:09.417: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 429s (umockdev-run:2192): GLib-GIO-DEBUG: 05:09:09.420: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 429s (process:2196): libfprint-context-DEBUG: 05:09:09.547: Initializing FpContext (libfprint version 1.94.9+tod1) 429s (process:2196): libfprint-tod-DEBUG: 05:09:09.547: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 429s (process:2196): libfprint-context-DEBUG: 05:09:09.550: No driver found for USB device 1D6B:0002 429s (process:2196): libfprint-device-DEBUG: 05:09:09.550: Device reported probe completion 429s (process:2196): libfprint-device-DEBUG: 05:09:09.550: Completing action FPI_DEVICE_ACTION_PROBE in idle! 429s (process:2196): libfprint-device-DEBUG: 05:09:09.550: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.553: [vfs7552] DEV_OPEN_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.553: [vfs7552] DEVICE OPEN entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.553: Sending vfs7552_cmd_01 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.554: [vfs7552] DEVICE OPEN entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.554: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.554: Got 38 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.554: [vfs7552] DEVICE OPEN entering state 2 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.554: Sending vfs7552_cmd_19 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.555: [vfs7552] DEVICE OPEN entering state 3 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.555: Receiving 128 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.555: Got 68 bytes out of 128 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.555: [vfs7552] DEVICE OPEN entering state 4 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.555: Sending vfs7552_init_00 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.556: [vfs7552] DEVICE OPEN entering state 5 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.556: Receiving 64 bytes 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.556: [vfs7552] DEVICE OPEN entering state 6 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.556: Sending vfs7552_init_01 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.557: [vfs7552] DEVICE OPEN entering state 7 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.557: Receiving 64 bytes 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.557: [vfs7552] DEVICE OPEN entering state 8 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.557: Sending vfs7552_init_02 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.558: [vfs7552] DEVICE OPEN entering state 9 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.558: Receiving 64 bytes 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.559: [vfs7552] DEVICE OPEN entering state 10 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.559: Sending vfs7552_init_03 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.559: [vfs7552] DEVICE OPEN entering state 11 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.559: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.560: Got 10 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.560: [vfs7552] DEVICE OPEN entering state 12 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.560: Sending vfs7552_init_04 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.560: [vfs7552] DEVICE OPEN entering state 13 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.560: Receiving 64 bytes 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.561: [vfs7552] DEVICE OPEN completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.561: [vfs7552] DEV_OPEN_NUM_STATES completed successfully 429s (process:2196): libfprint-image_device-DEBUG: 05:09:09.561: Image device open completed 429s (process:2196): libfprint-device-DEBUG: 05:09:09.561: Device reported open completion 429s (process:2196): libfprint-device-DEBUG: 05:09:09.561: Completing action FPI_DEVICE_ACTION_OPEN in idle! 429s (process:2196): libfprint-device-DEBUG: 05:09:09.561: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 429s (process:2196): libfprint-device-DEBUG: 05:09:09.561: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 429s (process:2196): libfprint-image_device-DEBUG: 05:09:09.561: Activating image device 429s (process:2196): libfprint-image_device-DEBUG: 05:09:09.562: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 429s (process:2196): libfprint-image_device-DEBUG: 05:09:09.562: Image device activation completed 429s (process:2196): libfprint-image_device-DEBUG: 05:09:09.562: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 429s (process:2196): libfprint-image_device-DEBUG: 05:09:09.562: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 429s (process:2196): libfprint-device-DEBUG: 05:09:09.562: Device reported finger status change: FP_FINGER_STATUS_NEEDED 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.611: changing to 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.611: [vfs7552] ACTIVATE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.611: [vfs7552] ACTIVATE INIT entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.611: Sending vfs7552_image_start 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.613: [vfs7552] ACTIVATE INIT entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.613: Receiving 2048 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.614: Got 1962 bytes out of 2048 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.614: [vfs7552] ACTIVATE INIT completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.614: [vfs7552] ACTIVATE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.614: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.614: Receiving 8 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.614: Got 5 bytes out of 8 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.614: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.614: [vfs7552] ACTIVATE_NUM_STATES entering state 2 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.614: [vfs7552] ACTIVATE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.614: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.614: Receiving 8 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.615: Got 5 bytes out of 8 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.615: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.615: [vfs7552] ACTIVATE_NUM_STATES entering state 2 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.615: [vfs7552] ACTIVATE_NUM_STATES entering state 3 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.615: [vfs7552] ACTIVATE_NUM_STATES completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.615: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.615: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.615: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.615: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.616: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.616: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.616: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.616: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.616: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.616: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.617: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.617: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.617: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.617: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.617: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.617: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.618: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.618: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.618: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.618: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.618: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.618: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.619: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.619: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.619: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.619: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.619: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.619: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.620: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.620: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.620: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.620: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.621: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.621: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.621: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.621: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.621: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.621: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.622: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.622: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.622: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.622: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.622: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.622: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.623: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.623: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.624: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.624: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.624: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.624: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.624: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.624: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.625: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.625: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.625: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.625: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.625: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.625: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.626: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.626: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.626: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.626: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.626: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.626: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.627: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.627: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.627: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.627: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.628: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.628: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.628: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.628: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.628: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.628: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.629: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.629: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.629: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.629: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.629: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.629: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.630: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.630: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.631: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.631: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.631: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.631: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.631: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.631: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.632: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.632: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.632: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.632: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.632: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.632: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.633: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.633: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.633: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.633: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.633: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.633: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.634: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.634: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.634: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.634: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.635: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.635: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.635: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.635: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.635: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.635: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.636: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.636: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.636: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.636: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.636: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.636: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.637: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.637: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.637: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.637: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.637: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.637: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.638: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.638: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.638: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.638: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.638: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.638: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.639: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.639: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.640: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.640: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.640: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.640: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.640: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.640: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.641: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.641: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.641: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.641: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.641: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.641: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.642: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.642: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.642: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.642: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.642: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.642: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.643: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.643: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.643: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.643: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.643: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.643: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.644: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.644: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.644: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.644: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.644: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.644: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.645: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.645: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.645: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.645: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.646: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.646: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.646: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.646: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.646: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.646: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.647: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.647: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.648: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.648: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.648: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.648: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.648: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.648: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.649: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.649: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.649: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.649: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.649: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.649: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.650: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.650: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.650: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.650: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.651: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.651: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.651: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.651: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.651: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.651: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.652: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.652: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.652: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.652: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.652: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.652: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.653: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.653: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.653: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.653: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.653: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.653: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.654: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.654: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.654: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.654: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.654: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.654: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.655: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.655: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.655: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.655: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.655: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.655: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.656: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.656: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.657: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.657: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.657: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.657: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.657: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.657: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.658: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.658: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.658: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.658: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.658: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.658: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.659: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.659: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.659: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.659: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.659: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.659: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.660: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.660: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.660: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.660: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.660: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.660: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.661: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.661: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.661: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.661: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.662: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.662: Receiving 64 bytes 429s (process:2196): libfprint-device-DEBUG: 05:09:09.662: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.662: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.662: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.662: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.662: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.663: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.663: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.663: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.663: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.663: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.663: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.664: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.664: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.664: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.664: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.664: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.664: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.665: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.665: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.665: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.665: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.665: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.665: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.666: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.666: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.666: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.666: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.666: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.666: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.667: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.667: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.668: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.668: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.668: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.668: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.668: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.668: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.669: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.669: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.669: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.669: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.670: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.670: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.670: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.670: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.670: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.670: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.671: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.671: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.671: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.671: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.671: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.671: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.672: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.672: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.672: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.672: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.672: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.672: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.673: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.673: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.674: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.674: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.674: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.674: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.674: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.674: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.675: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.675: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.675: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.675: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.675: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.675: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.676: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.676: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.676: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.676: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.677: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.677: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.677: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.677: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.677: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.677: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.678: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.678: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.678: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.678: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.678: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.678: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.679: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.679: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.680: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.680: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.680: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.680: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.680: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.680: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.681: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.681: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.681: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.681: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.681: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.681: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.682: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.682: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.682: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.682: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.682: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.682: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.683: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.683: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.683: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.683: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.684: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.684: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.684: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.684: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.684: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.684: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.685: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.685: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.685: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.685: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.685: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.685: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.686: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.686: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.686: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.687: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.687: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.687: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.687: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.687: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.688: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.688: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.688: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.688: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.688: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.688: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.689: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.689: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.689: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.689: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.689: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.689: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.690: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.690: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.690: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.690: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.690: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.690: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.691: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.691: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.691: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.691: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.691: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.691: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.692: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.692: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.692: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.692: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.693: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.693: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.693: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.693: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.693: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.693: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.694: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.694: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.694: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.694: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.694: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.694: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.695: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.695: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.696: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.696: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.696: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.696: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.696: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.696: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.697: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.697: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.697: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.697: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.697: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.697: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.698: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.698: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.698: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.698: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.698: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.698: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.699: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.699: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.699: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.699: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.699: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.699: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.700: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.700: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.700: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.700: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.700: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.700: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.701: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.701: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.701: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.701: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.702: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.702: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.702: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.702: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.702: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.702: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.703: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.703: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.703: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.703: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.703: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.703: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.704: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.704: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.704: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.704: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.704: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.704: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.705: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.705: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.705: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.705: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.705: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.705: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.706: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.706: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.707: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.707: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.707: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.707: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.707: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.707: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.708: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.708: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.708: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.708: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.708: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.708: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.709: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.709: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.709: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.709: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.710: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.710: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.710: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.710: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.710: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.710: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.711: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.711: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.711: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.711: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.711: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.711: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.712: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.712: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.712: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.712: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.712: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.712: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.713: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.713: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.713: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.713: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.713: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.713: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.714: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.714: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.715: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.715: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.715: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.715: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.715: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.715: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.716: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.716: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.716: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.716: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.716: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.716: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.717: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.717: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.717: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.717: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.717: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.717: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.718: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.718: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.718: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.718: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.718: Sending vfs7552_read_image_chunk 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.718: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.718: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.719: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.719: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.719: Sending vfs7552_read_image_chunk 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.720: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.720: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.720: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.720: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.720: Sending vfs7552_read_image_chunk 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.721: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.721: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.721: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.721: variance_before = 396 429s 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.721: background stored 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.721: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.721: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.722: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.722: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.723: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.723: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.723: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.723: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.723: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.723: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.724: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.724: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.724: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.724: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.724: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.724: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.725: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.725: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.725: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.725: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.725: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.725: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.726: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.726: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.726: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.726: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.727: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.727: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.727: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.727: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.727: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.727: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.728: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.728: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.728: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.728: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.728: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.728: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.729: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.729: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.729: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.730: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.730: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.730: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.730: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.730: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.731: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.731: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.731: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.731: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.731: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.731: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.732: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.732: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.732: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.732: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.732: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.732: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.733: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.733: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.733: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.733: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.733: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.733: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.734: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.734: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.734: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.734: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.735: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.735: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.735: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.735: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.735: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.735: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.736: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.736: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.736: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.736: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.736: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.736: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.737: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.737: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.737: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.737: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.737: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.737: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.738: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.738: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.738: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.738: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.738: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.738: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.739: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.739: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.740: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.740: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.740: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.740: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.740: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.740: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.741: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.741: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.741: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.741: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.741: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.741: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.742: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.742: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.742: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.742: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.742: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.742: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.743: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.743: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.743: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.743: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.743: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.743: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.744: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.744: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.744: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.744: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.744: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.744: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.745: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.745: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.745: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.745: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.745: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.745: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.746: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.746: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.746: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.746: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.746: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.746: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.747: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.747: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.747: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.747: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.748: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.748: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.748: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.748: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.748: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.748: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.749: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.749: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.749: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.749: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.749: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.749: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.750: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.750: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.750: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.750: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.750: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.750: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.751: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.751: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.751: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.751: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.751: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.751: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.752: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.752: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.752: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.752: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.752: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.752: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.753: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.753: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.753: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.753: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.753: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.753: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.754: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.754: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.754: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.754: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.754: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.754: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.755: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.755: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.756: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.756: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.756: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.756: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.756: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.756: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.757: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.757: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.757: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.757: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.757: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.757: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.758: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.758: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.758: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.758: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.758: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.758: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.759: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.759: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.759: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.759: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.759: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.759: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.760: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.760: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.760: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.760: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.760: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.760: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.761: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.761: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.761: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.761: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.761: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.761: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.762: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.762: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.762: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.762: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.762: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.762: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.763: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.763: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.763: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.763: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.764: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.764: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.764: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.764: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.764: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.764: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.765: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.765: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.765: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.765: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.765: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.765: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.766: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.766: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.766: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.766: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.766: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.766: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.767: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.767: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.767: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.767: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.767: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.767: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.768: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.768: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.768: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.768: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.769: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.769: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.769: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.769: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.770: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.770: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.770: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.770: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.770: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.770: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.771: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.771: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.771: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.771: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.771: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.771: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.772: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.772: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.772: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.772: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.772: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.772: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.773: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.773: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.773: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.773: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.773: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.773: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.774: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.774: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.774: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.774: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.774: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.774: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.775: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.775: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.775: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.775: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.776: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.776: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.776: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.776: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.776: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.776: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.777: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.777: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.777: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.777: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.777: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.777: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.778: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.778: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.778: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.778: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.778: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.778: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.779: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.779: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.779: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.779: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.779: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.779: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.780: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.780: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.780: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.780: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.780: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.780: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.781: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.781: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.782: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.782: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.782: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.782: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.782: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.782: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.783: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.783: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.783: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.783: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.783: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.783: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.784: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.784: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.784: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.784: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.785: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.785: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.785: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.785: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.785: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.785: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.786: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.786: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.786: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.786: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.786: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.786: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.787: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.787: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.787: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.787: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.787: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.787: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.788: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.788: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.789: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.789: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.789: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.789: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.789: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.789: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.790: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.790: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.790: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.790: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.790: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.790: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.791: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.791: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.791: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.791: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.791: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.791: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.792: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.792: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.792: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.792: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.792: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.792: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.793: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.793: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.793: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.793: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.793: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.793: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.794: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.794: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.794: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.794: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.794: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.794: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.795: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.795: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.795: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.795: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.795: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.795: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.796: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.796: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.796: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.796: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.797: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.797: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.797: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.797: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.797: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.797: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.798: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.798: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.798: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.798: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.798: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.798: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.799: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.799: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.799: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.799: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.799: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.799: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.800: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.800: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.800: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.800: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.800: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.800: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.801: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.801: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.801: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.801: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.802: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.802: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.802: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.802: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.803: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.803: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.803: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.803: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.803: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.803: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.804: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.804: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.804: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.804: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.804: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.804: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.805: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.805: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.805: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.805: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.805: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.805: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.806: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.806: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.806: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.806: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.806: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.806: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.807: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.807: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.807: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.807: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.808: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.808: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.808: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.808: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.808: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.808: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.809: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.809: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.809: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.809: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.809: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.809: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.810: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.810: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.810: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.810: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.810: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.810: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.811: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.811: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.811: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.811: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.811: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.811: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.812: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.812: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.812: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.812: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.813: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.813: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.813: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.813: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.814: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.814: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.814: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.814: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.814: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.814: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.815: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.815: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.815: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.815: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.815: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.815: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.816: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.816: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.816: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.816: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.816: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.816: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.817: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.817: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.817: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.817: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.817: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.817: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.818: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.818: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.818: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.818: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.819: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.819: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.819: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.819: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.819: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.819: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.820: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.820: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.820: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.820: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.820: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.820: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.821: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.821: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.821: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.821: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.821: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.821: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.822: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.822: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.822: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.822: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.822: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.822: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.823: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.823: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.823: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.823: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.823: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.823: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.824: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.824: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.824: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.824: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.824: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.824: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.825: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.825: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.825: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.825: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.825: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.825: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.826: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.826: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.827: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.827: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.827: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.827: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.827: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.827: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.828: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.828: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.828: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.828: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.828: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.828: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.829: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.829: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.829: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.829: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.829: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.829: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.830: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.830: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.830: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.830: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.830: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.830: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.831: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.831: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.831: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.831: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.832: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.832: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.832: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.832: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.832: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.832: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.833: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.833: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.833: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.833: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.833: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.833: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.834: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.834: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.834: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.834: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.834: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.834: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.835: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.835: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.835: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.835: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.835: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.835: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.835: Sending vfs7552_read_image_chunk 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.836: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.836: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.837: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.837: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.837: Sending vfs7552_read_image_chunk 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.837: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.837: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.838: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.838: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.838: Sending vfs7552_read_image_chunk 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.838: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.838: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.839: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.839: Cleaning image 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.839: variance_after = 20 429s 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.839: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.839: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.839: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.839: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.840: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.840: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.840: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.840: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.840: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.840: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.841: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.841: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.841: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.841: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.842: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.842: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.842: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.842: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.842: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.842: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.843: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.843: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.843: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.843: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.843: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.843: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.844: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.844: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.844: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.844: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.844: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.844: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.845: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.845: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.845: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.845: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.845: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.845: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.846: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.846: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.846: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.846: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.846: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.846: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.847: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.847: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.847: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.847: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.848: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.848: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.848: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.848: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.849: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.849: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.849: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.849: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.849: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.849: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.850: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.850: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.850: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.850: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.850: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.850: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.851: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.851: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.851: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.851: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.851: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.851: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.852: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.852: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.852: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.852: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.852: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.852: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.853: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.853: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.853: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.853: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.853: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.853: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.854: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.854: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.854: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.854: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.854: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.854: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.855: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.855: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.855: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.855: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.856: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.856: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.856: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.856: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.856: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.856: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.857: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.857: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.857: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.857: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.857: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.857: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.858: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.858: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.858: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.858: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.858: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.858: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.859: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.859: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.859: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.859: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.859: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.859: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.860: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.860: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.860: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.860: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.860: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.860: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.861: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.861: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.861: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.861: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.862: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.862: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.862: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.862: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.863: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.863: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.863: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.863: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.863: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.863: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.864: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.864: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.864: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.864: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.864: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.864: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.865: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.865: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.865: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.865: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.865: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.865: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.866: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.866: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.866: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.866: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.866: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.866: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.867: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.867: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.867: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.867: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.868: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.868: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.868: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.868: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.868: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.868: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.869: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.869: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.869: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.869: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.869: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.869: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.870: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.870: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.870: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.870: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.870: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.870: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.871: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.871: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.871: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.871: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.871: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.871: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.872: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.872: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.873: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.873: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.873: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.873: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.873: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.873: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.874: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.874: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.874: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.874: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.874: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.874: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.875: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.875: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.875: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.875: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.875: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.875: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.876: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.876: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.876: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.876: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.876: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.876: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.877: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.877: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.877: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.877: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.877: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.877: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.878: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.878: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.878: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.878: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.879: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.879: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.879: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.879: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.879: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.879: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.880: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.880: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.880: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.880: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.880: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.880: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.881: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.881: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.881: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.881: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.881: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.881: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.882: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.882: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.882: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.882: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.882: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.882: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.883: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.883: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.883: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.883: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.884: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.884: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.884: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.884: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.885: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.885: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.885: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.885: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.885: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.885: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.886: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.886: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.886: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.886: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.886: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.886: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.887: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.887: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.887: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.887: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.887: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.887: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.888: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.888: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.888: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.888: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.888: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.888: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.889: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.889: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.889: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.889: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.889: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.889: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.890: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.890: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.890: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.890: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.890: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.890: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.891: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.891: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.891: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.891: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.892: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.892: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.892: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.892: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.892: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.892: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.893: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.893: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.893: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.893: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.893: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.893: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.894: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.894: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.894: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.895: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.895: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.895: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.895: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.895: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.896: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.896: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.896: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.896: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.896: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.896: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.897: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.897: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.897: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.897: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.897: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.897: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.898: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.898: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.898: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.898: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.898: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.898: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.899: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.899: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.899: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.899: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.899: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.899: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.900: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.900: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.900: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.900: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.900: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.900: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.901: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.901: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.901: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.901: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.902: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.902: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.902: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.902: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.902: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.902: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.903: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.903: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.903: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.903: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.904: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.904: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.904: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.904: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.905: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.905: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.905: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.905: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.906: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.906: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.906: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.906: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.906: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.906: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.907: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.907: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.907: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.907: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.907: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.907: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.907: Sending vfs7552_read_image_chunk 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.908: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.908: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.909: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.909: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.909: Sending vfs7552_read_image_chunk 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.909: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.909: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.910: [vfs7552] CAPTURE_NUM_STATES entering state 2 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.910: [vfs7552] REQUEST CHUNK entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.910: Sending vfs7552_read_image_chunk 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.911: [vfs7552] REQUEST CHUNK completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.911: [vfs7552] CAPTURE_NUM_STATES entering state 3 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.911: [vfs7552] CAPTURE_NUM_STATES entering state 4 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.911: Cleaning image 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.912: variance_after = 18 429s 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.912: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.912: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.912: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.912: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.913: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.913: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.913: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.913: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.914: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.914: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.915: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.915: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.915: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.915: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.915: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.915: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.916: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.916: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.916: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.916: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.917: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.917: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.918: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.918: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.918: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.918: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.919: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.919: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.919: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.919: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.919: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.919: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.920: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.920: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.921: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.921: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.921: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.921: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.921: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.921: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.922: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.922: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.922: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.922: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.923: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.923: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.923: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.923: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.923: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.923: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.924: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.924: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.924: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.924: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.924: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.924: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.925: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.925: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.926: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.926: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.926: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.926: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.926: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.926: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.927: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.927: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.927: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.927: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.927: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.927: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.928: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.928: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.928: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.928: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.929: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.929: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.929: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.929: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.929: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.929: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.930: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.930: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.930: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.930: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.930: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.930: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.931: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.931: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.932: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.932: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.932: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.932: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.932: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.932: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.933: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.933: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.933: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.933: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.933: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.933: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.934: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.934: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.934: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.934: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.934: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.934: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.935: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.935: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.935: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.935: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.936: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.936: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.936: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.936: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.936: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.936: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.937: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.937: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.937: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.937: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.937: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.937: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.938: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.938: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.939: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.939: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.939: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.939: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.939: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.939: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.940: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.940: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.940: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.940: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.940: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.940: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.941: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.941: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.941: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.941: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.942: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.942: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.942: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.942: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.942: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.942: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.943: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.943: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.943: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.943: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.943: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.943: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.944: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.944: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.944: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.945: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.945: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.945: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.945: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.945: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.946: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.946: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.946: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.946: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.946: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.946: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.947: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.947: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.947: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.947: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.947: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.947: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.948: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.948: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.948: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.948: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.949: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.949: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.949: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.949: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.949: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.949: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.950: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.950: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.950: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.950: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.950: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.950: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.951: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.951: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.952: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.952: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.952: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.952: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.952: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.952: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.953: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.953: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.953: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.953: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.953: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.953: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.954: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.954: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.954: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.954: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.954: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.954: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.955: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.955: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.955: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.955: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.955: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.956: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.956: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.956: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.956: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.956: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.957: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.957: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.957: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.957: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.957: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.957: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.958: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.958: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.958: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.958: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.958: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.958: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.959: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.959: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.959: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.959: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.959: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.959: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.960: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.960: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.961: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.961: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.961: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.961: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.961: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.961: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.962: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.962: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.962: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.962: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.962: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.962: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.963: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.963: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.963: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.963: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.963: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.963: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.964: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.964: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.964: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.964: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.964: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.964: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.965: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.965: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.965: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.965: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.965: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.966: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.966: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.966: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.966: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.966: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.967: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.967: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.967: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.967: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.967: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.967: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.968: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.968: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.968: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.968: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.968: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.968: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.969: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.969: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.969: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.969: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.969: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.969: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.970: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.970: Receiving 64 bytes 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.970: Got 6 bytes out of 64 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.970: [vfs7552] QUERY DATA READY completed successfully 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.970: [vfs7552] QUERY DATA READY entering state 0 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.970: Sending vfs7552_is_image_ready 429s (process:2196): libfprint-SSM-DEBUG: 05:09:09.971: [vfs7552] QUERY DATA READY entering state 1 429s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.971: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.971: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.971: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.971: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.971: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.972: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.972: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.972: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.972: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.972: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.972: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.973: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.973: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.974: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.974: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.974: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.974: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.974: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.974: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.975: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.975: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.975: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.975: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.975: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.975: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.976: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.976: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.976: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.976: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.976: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.976: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.977: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.977: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.977: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.977: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.977: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.977: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.978: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.978: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.978: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.978: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.978: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.978: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.979: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.979: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.979: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.979: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.979: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.979: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.980: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.980: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.980: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.980: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.980: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.980: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.981: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.981: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.981: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.981: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.981: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.982: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.982: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.982: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.982: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.982: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.983: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.983: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.983: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.983: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.983: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.983: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.984: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.984: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.984: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.984: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.984: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.984: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.985: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.985: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.985: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.985: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.985: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.985: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.986: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.986: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.986: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.986: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.986: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.986: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.987: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.987: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.987: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.987: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.987: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.987: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.988: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.988: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.989: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.989: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.989: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.989: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.989: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.989: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.990: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.990: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.990: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.990: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.990: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.990: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.991: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.991: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.991: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.991: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.991: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.991: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.992: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.992: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.992: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.992: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.992: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.992: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.993: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.993: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.993: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.993: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.993: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.993: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.994: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.994: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.994: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.994: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.994: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.994: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.995: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.995: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.995: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.995: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.996: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.996: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.996: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.996: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.996: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.996: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.997: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.997: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.997: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.997: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.997: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.997: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.998: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.998: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.998: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.998: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.998: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.998: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.999: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.999: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.999: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.999: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:09.999: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:09.999: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.000: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.000: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.000: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.000: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.000: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.000: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.001: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.001: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.001: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.002: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.002: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.002: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.002: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.002: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.003: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.003: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.003: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.003: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.003: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.003: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.004: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.004: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.004: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.004: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.004: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.004: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.005: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.005: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.005: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.005: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.005: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.005: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.006: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.006: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.006: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.006: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.006: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.006: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.007: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.007: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.007: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.007: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.007: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.007: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.008: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.008: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.008: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.008: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.009: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.009: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.009: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.009: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.009: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.009: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.010: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.010: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.010: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.010: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.010: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.010: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.011: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.011: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.012: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.012: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.012: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.012: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.012: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.012: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.013: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.013: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.013: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.013: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.013: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.013: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.014: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.014: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.014: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.014: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.014: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.014: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.015: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.015: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.015: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.015: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.015: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.015: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.016: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.016: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.016: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.016: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.016: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.016: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.017: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.017: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.017: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.017: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.018: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.018: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.018: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.018: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.018: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.018: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.019: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.019: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.019: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.019: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.019: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.019: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.020: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.020: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.021: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.021: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.021: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.021: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.021: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.021: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.022: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.022: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.022: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.022: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.022: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.022: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.023: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.023: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.023: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.023: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.023: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.023: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.024: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.024: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.024: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.024: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.024: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.024: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.025: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.025: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.025: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.025: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.025: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.026: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.026: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.026: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.026: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.026: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.027: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.027: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.027: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.027: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.027: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.027: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.028: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.028: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.028: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.028: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.028: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.028: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.029: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.029: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.030: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.030: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.030: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.030: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.030: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.030: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.031: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.031: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.031: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.031: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.031: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.031: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.032: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.032: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.032: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.032: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.032: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.032: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.033: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.033: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.033: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.033: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.033: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.033: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.034: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.034: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.034: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.034: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.034: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.034: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.035: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.035: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.035: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.035: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.035: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.035: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.036: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.036: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.036: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.036: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.036: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.037: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.037: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.037: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.037: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.037: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.038: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.038: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.038: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.038: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.038: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.038: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.039: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.039: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.039: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.039: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.039: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.039: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.040: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.040: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.040: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.040: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.040: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.040: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.041: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.041: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.041: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.041: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.041: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.041: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.042: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.042: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.042: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.042: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.042: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.042: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.043: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.043: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.043: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.043: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.043: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.043: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.044: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.044: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.045: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.045: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.045: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.045: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.045: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.045: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.046: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.046: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.046: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.046: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.046: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.046: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.047: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.047: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.047: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.047: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.047: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.047: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.048: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.048: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.048: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.048: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.048: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.048: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.049: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.049: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.049: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.049: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.049: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.049: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.050: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.050: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.050: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.050: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.050: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.050: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.051: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.051: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.051: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.051: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.052: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.052: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.052: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.052: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.052: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.052: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.053: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.053: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.053: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.053: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.053: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.053: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.054: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.054: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.054: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.054: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.054: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.054: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.055: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.055: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.055: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.055: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.055: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.055: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.056: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.056: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.057: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.057: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.057: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.057: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.057: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.057: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.058: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.058: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.058: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.058: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.058: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.058: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.059: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.059: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.059: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.059: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.059: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.059: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.060: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.060: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.060: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.060: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.060: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.061: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.061: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.061: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.061: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.061: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.062: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.062: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.062: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.062: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.062: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.062: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.063: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.063: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.063: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.063: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.063: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.063: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.064: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.064: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.064: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.064: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.064: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.064: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.065: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.065: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.066: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.066: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.066: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.066: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.066: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.066: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.067: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.067: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.067: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.067: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.067: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.067: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.068: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.068: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.068: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.068: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.068: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.068: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.069: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.069: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.069: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.069: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.069: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.069: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.070: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.070: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.070: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.070: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.071: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.071: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.071: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.071: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.071: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.071: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.072: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.072: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.073: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.073: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.073: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.073: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.073: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.073: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.074: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.074: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.074: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.074: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.074: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.074: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.075: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.075: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.075: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.075: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.075: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.075: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.076: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.076: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.076: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.076: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.076: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.077: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.077: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.077: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.077: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.077: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.078: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.078: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.078: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.078: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.078: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.078: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.079: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.079: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.079: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.079: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.079: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.079: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.080: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.080: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.080: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.080: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.080: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.080: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.081: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.081: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.081: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.081: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.081: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.081: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.082: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.082: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.082: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.082: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.082: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.082: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.083: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.083: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.084: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.084: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.084: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.084: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.084: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.084: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.085: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.085: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.085: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.085: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.085: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.085: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.086: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.086: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.086: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.086: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.086: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.086: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.087: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.087: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.087: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.087: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.087: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.087: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.088: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.088: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.088: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.088: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.089: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.089: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.089: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.089: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.089: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.089: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.090: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.090: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.090: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.090: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.090: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.090: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.091: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.091: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.091: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.091: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.091: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.091: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.092: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.092: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.092: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.092: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.093: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.093: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.093: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.093: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.094: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.094: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.094: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.094: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.094: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.094: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.095: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.095: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.095: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.095: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.095: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.095: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.096: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.096: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.096: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.096: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.096: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.096: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.097: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.097: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.097: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.097: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.097: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.097: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.098: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.098: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.098: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.098: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.098: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.098: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.099: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.099: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.099: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.099: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.100: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.100: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.100: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.100: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.100: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.100: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.101: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.101: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.101: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.101: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.101: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.101: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.102: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.102: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.102: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.102: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.102: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.102: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.103: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.103: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.103: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.103: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.103: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.103: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.104: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.104: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.105: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.105: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.105: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.105: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.105: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.105: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.106: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.106: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.106: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.106: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.106: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.106: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.107: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.107: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.107: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.107: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.107: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.107: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.108: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.108: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.108: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.108: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.108: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.108: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.108: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.109: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.109: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.109: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.109: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.109: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.110: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.110: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.110: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.111: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.111: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.111: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.111: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.111: variance_after = 20 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.111: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.111: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.112: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.112: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.112: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.112: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.112: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.112: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.113: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.113: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.114: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.114: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.114: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.114: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.114: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.114: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.115: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.115: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.115: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.115: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.115: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.115: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.116: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.116: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.116: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.116: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.116: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.116: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.117: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.117: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.117: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.117: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.117: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.117: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.118: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.118: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.118: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.118: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.119: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.119: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.119: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.119: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.119: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.119: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.120: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.120: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.120: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.120: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.120: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.120: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.121: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.121: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.121: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.121: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.122: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.122: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.122: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.122: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.123: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.123: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.123: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.123: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.123: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.123: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.124: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.124: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.124: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.124: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.124: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.124: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.125: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.125: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.125: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.125: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.125: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.125: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.126: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.126: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.126: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.126: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.126: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.126: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.127: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.127: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.127: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.127: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.128: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.128: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.128: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.128: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.128: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.128: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.129: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.129: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.129: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.129: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.129: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.129: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.130: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.130: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.130: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.130: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.130: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.130: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.131: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.131: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.131: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.132: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.132: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.132: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.132: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.132: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.133: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.133: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.133: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.133: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.133: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.133: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.134: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.134: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.134: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.134: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.134: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.134: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.135: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.135: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.135: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.135: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.135: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.135: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.136: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.136: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.136: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.136: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.136: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.136: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.137: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.137: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.137: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.137: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.138: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.138: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.138: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.138: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.138: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.138: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.139: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.139: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.139: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.139: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.139: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.139: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.140: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.140: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.140: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.140: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.140: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.140: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.141: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.141: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.141: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.141: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.141: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.141: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.142: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.142: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.143: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.143: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.143: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.143: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.143: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.143: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.144: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.144: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.144: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.144: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.144: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.144: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.145: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.145: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.145: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.145: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.145: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.145: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.146: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.146: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.146: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.146: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.146: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.146: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.147: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.147: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.147: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.147: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.148: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.148: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.148: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.148: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.148: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.148: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.149: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.149: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.149: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.149: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.149: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.149: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.150: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.150: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.151: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.151: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.151: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.151: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.151: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.151: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.152: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.152: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.152: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.152: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.153: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.153: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.153: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.153: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.153: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.153: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.154: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.154: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.154: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.154: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.154: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.154: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.155: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.155: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.155: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.155: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.156: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.156: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.156: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.156: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.157: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.157: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.157: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.157: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.157: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.157: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.158: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.158: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.158: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.158: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.158: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.158: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.159: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.159: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.159: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.159: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.159: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.159: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.160: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.160: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.160: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.160: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.161: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.161: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.161: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.161: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.161: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.161: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.162: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.162: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.162: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.162: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.162: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.162: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.163: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.163: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.163: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.163: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.163: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.163: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.164: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.164: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.164: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.164: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.164: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.164: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.165: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.165: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.165: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.166: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.166: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.166: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.166: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.166: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.167: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.167: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.167: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.167: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.167: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.167: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.168: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.168: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.168: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.168: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.168: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.168: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.169: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.169: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.169: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.169: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.169: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.169: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.170: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.170: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.170: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.170: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.170: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.170: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.171: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.171: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.171: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.171: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.172: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.172: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.172: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.172: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.172: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.172: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.172: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.173: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.173: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.173: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.173: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.173: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.174: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.174: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.174: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.174: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.174: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.175: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.175: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.176: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.176: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.176: variance_after = 18 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.176: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.176: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.176: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.176: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.177: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.177: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.177: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.177: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.177: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.177: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.178: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.178: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.178: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.178: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.178: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.178: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.179: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.179: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.179: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.179: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.179: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.179: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.180: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.180: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.180: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.180: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.181: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.181: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.181: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.181: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.181: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.181: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.182: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.182: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.182: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.182: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.182: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.182: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.183: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.183: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.183: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.183: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.184: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.184: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.184: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.184: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.185: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.185: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.185: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.185: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.185: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.185: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.186: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.186: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.186: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.186: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.186: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.186: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.187: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.187: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.187: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.187: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.187: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.187: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.188: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.188: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.188: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.188: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.188: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.188: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.189: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.189: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.189: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.189: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.189: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.189: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.190: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.190: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.190: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.190: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.190: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.190: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.191: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.191: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.191: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.191: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.192: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.192: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.192: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.192: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.192: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.192: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.193: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.193: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.193: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.193: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.193: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.193: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.194: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.194: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.194: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.194: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.194: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.194: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.195: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.195: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.195: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.195: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.195: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.195: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.196: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.196: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.197: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.197: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.197: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.197: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.197: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.197: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.198: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.198: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.198: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.198: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.198: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.198: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.199: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.199: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.199: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.199: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.199: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.199: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.200: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.200: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.200: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.200: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.200: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.200: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.201: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.201: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.201: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.201: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.202: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.202: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.202: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.202: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.202: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.202: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.203: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.203: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.203: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.203: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.203: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.203: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.204: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.204: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.204: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.204: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.204: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.204: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.205: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.205: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.206: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.206: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.206: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.206: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.206: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.206: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.207: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.207: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.207: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.207: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.207: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.207: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.208: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.208: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.208: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.208: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.209: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.209: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.209: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.209: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.209: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.209: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.210: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.210: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.210: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.210: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.210: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.210: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.211: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.211: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.211: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.211: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.211: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.211: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.212: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.212: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.213: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.213: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.213: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.213: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.213: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.213: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.214: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.214: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.214: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.214: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.214: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.214: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.215: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.215: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.215: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.215: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.215: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.215: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.216: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.216: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.216: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.216: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.217: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.217: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.217: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.217: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.217: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.217: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.218: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.218: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.218: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.218: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.218: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.218: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.219: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.219: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.219: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.219: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.219: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.219: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.220: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.220: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.220: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.220: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.220: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.220: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.221: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.221: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.221: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.221: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.221: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.222: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.222: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.222: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.223: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.223: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.223: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.223: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.223: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.223: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.224: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.224: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.224: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.224: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.224: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.224: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.225: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.225: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.225: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.225: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.225: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.225: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.226: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.226: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.226: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.226: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.226: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.226: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.227: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.227: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.227: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.227: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.227: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.227: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.228: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.228: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.228: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.228: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.228: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.229: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.229: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.229: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.229: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.229: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.230: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.230: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.230: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.230: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.230: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.230: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.231: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.231: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.231: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.231: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.231: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.231: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.232: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.232: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.232: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.232: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.232: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.232: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.233: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.233: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.233: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.233: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.233: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.233: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.234: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.234: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.235: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.235: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.235: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.235: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.235: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.235: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.236: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.236: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.236: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.236: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.236: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.236: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.237: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.237: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.237: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.237: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.237: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.237: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.237: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.238: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.238: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.238: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.238: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.238: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.239: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.239: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.239: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.240: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.240: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.240: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.240: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.240: variance_after = 18 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.240: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.240: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.241: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.241: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.241: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.241: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.241: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.241: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.242: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.242: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.242: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.242: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.242: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.242: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.243: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.243: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.243: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.243: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.243: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.243: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.244: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.244: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.245: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.245: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.245: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.245: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.245: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.245: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.246: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.246: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.246: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.246: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.246: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.246: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.247: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.247: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.247: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.247: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.247: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.247: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.248: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.248: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.248: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.248: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.249: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.249: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.249: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.249: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.249: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.249: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.250: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.250: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.250: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.250: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.250: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.250: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.251: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.251: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.251: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.251: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.251: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.251: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.252: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.252: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.253: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.253: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.253: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.253: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.253: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.253: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.254: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.254: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.254: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.254: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.254: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.254: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.255: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.255: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.255: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.255: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.256: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.256: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.256: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.256: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.256: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.256: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.257: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.257: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.257: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.257: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.257: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.257: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.258: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.258: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.258: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.258: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.258: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.258: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.259: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.259: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.260: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.260: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.260: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.260: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.260: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.260: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.261: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.261: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.261: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.261: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.261: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.261: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.262: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.262: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.262: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.262: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.262: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.262: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.263: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.263: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.263: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.263: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.263: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.263: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.264: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.264: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.264: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.264: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.265: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.265: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.265: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.265: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.265: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.265: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.266: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.266: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.266: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.266: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.266: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.266: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.267: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.267: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.267: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.267: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.267: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.267: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.268: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.268: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.268: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.268: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.268: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.268: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.269: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.269: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.269: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.269: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.269: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.269: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.270: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.270: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.271: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.271: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.271: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.271: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.271: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.271: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.272: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.272: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.272: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.272: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.272: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.272: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.273: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.273: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.273: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.273: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.273: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.273: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.274: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.274: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.274: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.274: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.274: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.274: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.275: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.275: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.275: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.275: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.275: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.275: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.276: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.276: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.276: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.276: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.276: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.276: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.277: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.277: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.277: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.277: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.278: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.278: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.278: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.278: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.278: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.278: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.279: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.279: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.279: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.279: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.279: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.279: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.280: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.280: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.280: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.280: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.280: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.280: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.281: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.281: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.281: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.282: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.282: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.282: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.282: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.282: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.283: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.283: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.283: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.283: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.283: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.283: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.284: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.284: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.284: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.284: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.284: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.284: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.285: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.285: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.285: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.285: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.285: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.285: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.286: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.286: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.286: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.286: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.287: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.287: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.288: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.288: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.288: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.288: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.288: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.288: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.289: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.289: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.289: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.289: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.289: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.289: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.290: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.290: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.290: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.290: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.291: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.291: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.291: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.291: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.291: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.291: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.292: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.292: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.293: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.293: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.293: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.293: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.293: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.293: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.294: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.294: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.294: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.294: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.294: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.294: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.295: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.295: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.295: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.295: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.295: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.295: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.296: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.296: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.296: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.296: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.297: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.297: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.297: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.297: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.297: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.297: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.298: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.298: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.298: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.298: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.298: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.298: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.299: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.299: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.299: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.299: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.299: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.299: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.300: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.300: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.300: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.300: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.300: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.300: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.301: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.301: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.302: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.302: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.302: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.302: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.302: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.302: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.303: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.303: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.303: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.303: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.303: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.303: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.304: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.304: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.304: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.304: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.304: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.304: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.305: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.305: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.305: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.305: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.306: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.306: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.306: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.306: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.306: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.306: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.307: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.307: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.307: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.307: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.307: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.307: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.308: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.308: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.308: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.308: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.308: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.308: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.309: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.309: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.310: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.310: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.310: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.310: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.310: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.310: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.311: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.311: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.311: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.311: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.311: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.311: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.312: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.312: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.312: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.312: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.312: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.312: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.313: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.313: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.313: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.313: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.314: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.314: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.314: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.314: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.314: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.314: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.315: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.315: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.315: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.315: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.315: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.315: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.316: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.316: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.316: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.316: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.316: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.316: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.317: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.317: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.317: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.317: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.318: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.318: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.318: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.318: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.319: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.319: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.319: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.319: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.319: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.319: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.320: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.320: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.320: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.320: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.320: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.320: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.321: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.321: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.321: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.321: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.321: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.321: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.322: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.322: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.322: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.322: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.323: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.323: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.323: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.323: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.323: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.323: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.324: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.324: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.324: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.324: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.324: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.324: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.325: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.325: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.325: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.325: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.325: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.325: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.326: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.326: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.326: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.326: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.326: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.326: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.327: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.327: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.327: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.328: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.328: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.328: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.328: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.328: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.329: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.329: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.329: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.329: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.329: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.329: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.330: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.330: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.330: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.330: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.330: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.330: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.331: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.331: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.331: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.331: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.331: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.331: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.332: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.332: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.332: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.332: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.333: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.333: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.333: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.333: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.333: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.333: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.334: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.334: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.334: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.334: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.334: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.334: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.335: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.335: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.335: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.335: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.335: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.335: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.336: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.336: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.336: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.336: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.336: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.336: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.337: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.337: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.337: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.337: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.337: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.337: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.338: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.338: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.338: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.338: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.338: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.339: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.339: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.339: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.340: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.340: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.340: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.340: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.340: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.340: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.341: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.341: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.341: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.341: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.341: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.341: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.341: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.342: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.342: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.342: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.342: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.342: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.343: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.343: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.343: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.344: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.344: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.344: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.344: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.344: variance_after = 18 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.344: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.344: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.345: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.345: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.345: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.345: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.345: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.345: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.346: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.346: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.347: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.347: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.347: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.347: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.347: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.347: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.348: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.348: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.348: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.348: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.348: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.348: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.349: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.349: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.349: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.349: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.349: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.350: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.350: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.350: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.350: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.350: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.351: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.351: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.351: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.351: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.351: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.351: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.352: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.352: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.352: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.352: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.352: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.352: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.353: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.353: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.353: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.354: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.354: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.354: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.354: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.354: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.355: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.355: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.355: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.355: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.355: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.355: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.356: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.356: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.356: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.356: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.356: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.356: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.357: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.357: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.357: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.357: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.357: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.357: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.358: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.358: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.358: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.358: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.359: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.359: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.359: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.359: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.359: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.359: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.360: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.360: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.360: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.360: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.360: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.360: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.361: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.361: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.361: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.361: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.361: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.361: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.362: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.362: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.363: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.363: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.363: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.363: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.363: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.363: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.364: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.364: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.364: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.364: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.364: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.364: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.365: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.365: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.365: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.365: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.365: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.365: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.366: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.366: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.366: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.366: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.366: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.366: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.367: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.367: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.367: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.367: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.367: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.367: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.368: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.368: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.368: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.368: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.369: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.369: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.369: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.369: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.369: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.369: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.370: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.370: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.370: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.370: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.370: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.370: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.371: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.371: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.371: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.371: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.371: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.371: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.372: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.372: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.372: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.373: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.373: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.373: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.373: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.373: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.374: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.374: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.374: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.374: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.374: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.374: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.375: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.375: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.375: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.375: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.375: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.375: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.376: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.376: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.376: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.376: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.376: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.376: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.377: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.377: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.377: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.377: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.377: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.377: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.378: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.378: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.378: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.378: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.379: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.379: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.379: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.379: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.379: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.379: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.380: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.380: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.380: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.380: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.380: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.380: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.381: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.381: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.381: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.381: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.381: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.381: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.382: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.382: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.383: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.383: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.383: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.383: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.383: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.383: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.384: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.384: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.384: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.384: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.384: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.384: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.385: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.385: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.385: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.385: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.385: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.385: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.386: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.386: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.386: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.386: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.386: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.386: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.387: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.387: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.387: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.387: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.388: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.388: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.388: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.388: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.388: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.388: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.389: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.389: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.389: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.389: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.389: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.389: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.390: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.390: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.391: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.391: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.391: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.391: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.391: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.391: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.392: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.392: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.392: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.392: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.392: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.392: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.393: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.393: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.393: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.393: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.393: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.393: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.394: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.394: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.394: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.394: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.395: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.395: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.395: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.395: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.395: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.395: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.396: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.396: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.396: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.396: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.396: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.396: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.397: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.397: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.397: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.397: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.397: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.398: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.398: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.398: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.399: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.399: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.399: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.399: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.399: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.399: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.400: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.400: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.400: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.400: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.400: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.400: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.401: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.401: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.401: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.401: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.401: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.401: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.402: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.402: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.402: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.402: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.403: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.403: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.403: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.403: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.403: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.403: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.404: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.404: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.404: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.404: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.404: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.404: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.405: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.405: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.405: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.405: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.405: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.405: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.406: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.406: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.407: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.407: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.407: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.407: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.407: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.407: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.408: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.408: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.408: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.408: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.408: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.408: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.409: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.409: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.409: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.409: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.409: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.409: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.410: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.410: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.410: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.410: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.411: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.411: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.411: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.411: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.411: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.411: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.412: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.412: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.412: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.412: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.412: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.412: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.413: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.413: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.413: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.413: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.413: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.413: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.414: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.414: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.414: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.415: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.415: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.415: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.415: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.415: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.416: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.416: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.416: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.416: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.416: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.416: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.417: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.417: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.417: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.417: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.417: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.417: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.418: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.418: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.418: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.418: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.418: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.418: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.419: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.419: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.419: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.419: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.419: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.419: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.420: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.420: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.420: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.420: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.420: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.420: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.421: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.421: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.421: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.421: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.422: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.422: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.422: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.422: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.422: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.422: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.423: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.423: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.423: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.423: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.423: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.423: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.424: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.424: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.424: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.424: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.424: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.424: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.425: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.425: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.425: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.425: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.425: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.425: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.426: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.426: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.426: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.426: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.426: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.426: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.427: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.427: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.428: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.428: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.428: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.428: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.428: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.428: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.429: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.429: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.429: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.429: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.429: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.429: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.430: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.430: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.430: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.430: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.430: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.430: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.431: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.431: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.431: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.431: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.431: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.431: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.432: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.432: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.432: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.432: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.433: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.433: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.433: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.433: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.433: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.433: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.434: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.434: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.434: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.434: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.434: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.434: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.435: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.435: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.435: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.435: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.435: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.435: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.436: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.436: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.436: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.436: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.436: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.436: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.437: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.437: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.438: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.438: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.438: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.438: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.438: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.438: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.439: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.439: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.439: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.439: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.439: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.439: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.440: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.440: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.440: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.440: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.441: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.441: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.441: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.441: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.441: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.441: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.442: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.442: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.442: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.442: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.442: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.442: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.443: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.443: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.443: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.443: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.443: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.443: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.444: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.444: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.444: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.444: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.444: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.444: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.445: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.445: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.446: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.446: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.446: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.446: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.446: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.446: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.447: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.447: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.447: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.447: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.447: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.447: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.448: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.448: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.448: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.448: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.448: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.448: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.449: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.449: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.449: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.449: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.449: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.449: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.450: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.450: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.450: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.450: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.451: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.451: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.451: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.451: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.451: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.451: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.452: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.452: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.452: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.452: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.452: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.452: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.453: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.453: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.453: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.453: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.453: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.453: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.454: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.454: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.455: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.455: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.455: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.455: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.455: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.455: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.456: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.456: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.456: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.456: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.456: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.456: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.457: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.457: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.457: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.457: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.457: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.457: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.457: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.458: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.458: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.458: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.459: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.459: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.459: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.459: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.459: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.460: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.460: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.460: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.460: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.460: variance_after = 18 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.460: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.460: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.461: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.461: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.461: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.461: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.461: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.461: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.463: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.463: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.463: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.463: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.463: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.463: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.464: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.464: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.464: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.464: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.464: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.464: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.465: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.465: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.466: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.466: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.466: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.466: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.466: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.466: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.467: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.467: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.467: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.467: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.467: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.467: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.468: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.468: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.468: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.468: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.468: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.468: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.469: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.469: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.469: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.469: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.470: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.470: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.470: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.470: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.470: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.470: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.471: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.471: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.471: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.471: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.471: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.471: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.472: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.472: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.472: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.472: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.472: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.472: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.473: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.473: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.473: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.473: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.473: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.473: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.475: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.475: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.476: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.476: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.476: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.476: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.477: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.477: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.477: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.477: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.478: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.478: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.479: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.479: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.479: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.479: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.479: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.479: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.480: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.480: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.480: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.480: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.480: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.480: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.481: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.481: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.482: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.482: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.482: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.482: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.482: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.482: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.483: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.483: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.483: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.483: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.483: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.483: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.484: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.484: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.484: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.484: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.485: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.485: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.485: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.485: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.485: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.485: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.486: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.486: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.486: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.486: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.486: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.486: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.487: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.487: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.487: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.487: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.487: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.487: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.488: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.488: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.489: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.489: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.489: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.489: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.489: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.489: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.490: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.490: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.490: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.490: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.490: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.490: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.491: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.491: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.491: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.491: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.492: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.492: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.492: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.492: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.492: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.492: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.493: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.493: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.493: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.493: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.493: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.493: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.494: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.494: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.494: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.494: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.495: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.495: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.495: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.495: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.496: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.496: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.496: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.496: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.496: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.496: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.497: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.497: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.497: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.497: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.497: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.497: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.498: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.498: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.498: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.498: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.498: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.498: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.499: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.499: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.499: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.499: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.500: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.500: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.500: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.500: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.500: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.500: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.501: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.501: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.501: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.501: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.501: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.501: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.502: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.502: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.502: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.503: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.503: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.503: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.503: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.503: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.504: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.504: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.504: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.504: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.504: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.504: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.505: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.505: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.505: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.505: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.505: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.505: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.506: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.506: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.506: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.506: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.507: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.507: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.507: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.507: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.507: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.507: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.508: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.508: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.508: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.508: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.508: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.508: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.509: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.509: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.510: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.510: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.510: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.510: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.510: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.510: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.511: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.511: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.511: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.511: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.511: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.511: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.512: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.512: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.512: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.512: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.513: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.513: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.513: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.513: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.513: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.513: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.513: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.514: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.514: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.514: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.514: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.514: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.515: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.515: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.516: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.516: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.516: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.516: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.516: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.517: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.517: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.517: variance_after = 17 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.517: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.517: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.517: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.517: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.519: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.519: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.519: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.519: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.520: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.520: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.521: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.521: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.521: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.521: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.522: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.522: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.522: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.522: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.522: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.522: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.523: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.523: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.523: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.523: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.523: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.523: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.524: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.524: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.524: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.524: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.524: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.524: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.525: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.525: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.525: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.525: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.525: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.525: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.526: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.526: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.527: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.527: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.527: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.527: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.527: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.527: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.528: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.528: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.528: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.528: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.529: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.529: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.529: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.529: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.529: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.529: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.530: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.530: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.530: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.530: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.530: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.530: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.531: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.531: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.531: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.531: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.531: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.531: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.532: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.532: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.532: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.532: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.532: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.532: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.533: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.533: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.533: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.533: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.533: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.533: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.534: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.534: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.534: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.534: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.534: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.534: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.535: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.535: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.535: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.536: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.536: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.536: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.536: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.536: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.537: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.537: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.537: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.537: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.537: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.537: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.538: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.538: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.538: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.538: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.538: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.538: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.539: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.539: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.539: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.539: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.539: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.539: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.540: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.540: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.540: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.540: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.540: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.540: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.541: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.541: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.541: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.541: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.541: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.541: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.542: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.542: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.542: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.542: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.542: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.542: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.543: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.543: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.543: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.543: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.543: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.543: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.544: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.544: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.544: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.544: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.544: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.544: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.545: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.545: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.545: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.545: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.545: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.545: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.546: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.546: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.546: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.546: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.546: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.546: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.547: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.547: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.547: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.547: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.547: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.547: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.548: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.548: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.548: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.548: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.548: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.548: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.549: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.549: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.549: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.549: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.549: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.549: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.550: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.550: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.550: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.550: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.551: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.551: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.551: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.551: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.551: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.551: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.552: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.552: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.552: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.552: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.552: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.552: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.553: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.553: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.553: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.553: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.553: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.553: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.554: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.554: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.554: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.554: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.554: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.554: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.555: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.555: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.555: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.555: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.555: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.555: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.556: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.556: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.556: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.556: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.556: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.556: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.557: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.557: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.558: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.558: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.558: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.558: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.558: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.558: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.559: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.559: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.559: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.559: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.559: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.559: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.560: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.560: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.560: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.560: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.560: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.560: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.561: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.561: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.561: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.561: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.561: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.561: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.562: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.562: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.562: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.562: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.562: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.562: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.563: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.563: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.563: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.563: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.564: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.564: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.564: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.564: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.564: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.564: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.565: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.565: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.565: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.565: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.565: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.565: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.565: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.566: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.566: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.566: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.566: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.566: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.567: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.567: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.567: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.567: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.567: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.568: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.568: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.569: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.569: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.569: variance_after = 16 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.569: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.569: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.569: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.569: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.570: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.570: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.570: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.570: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.570: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.570: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.571: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.571: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.571: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.571: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.571: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.571: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.572: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.572: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.572: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.572: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.572: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.572: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.573: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.573: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.573: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.573: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.573: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.573: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.574: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.574: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.574: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.574: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.574: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.574: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.575: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.575: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.575: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.575: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.576: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.576: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.576: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.576: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.576: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.576: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.577: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.577: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.577: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.577: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.577: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.577: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.578: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.578: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.578: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.578: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.578: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.578: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.579: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.579: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.579: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.579: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.579: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.579: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.580: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.580: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.580: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.580: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.580: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.581: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.581: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.581: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.581: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.582: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.582: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.582: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.582: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.582: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.583: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.583: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.583: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.583: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.583: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.583: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.583: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.584: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.584: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.584: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.584: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.584: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.585: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.585: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.585: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.585: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.585: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.585: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.586: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.586: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.586: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.586: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.586: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.586: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.587: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.587: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.587: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.587: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.587: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.587: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.588: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.588: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.588: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.588: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.588: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.588: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.589: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.589: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.589: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.589: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.589: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.589: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.590: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.590: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.590: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.590: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.590: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.590: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.591: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.591: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.591: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.591: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.591: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.591: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.592: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.592: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.592: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.592: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.592: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.592: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.593: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.593: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.593: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.593: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.593: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.593: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.594: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.594: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.594: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.594: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.594: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.594: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.595: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.595: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.595: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.595: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.595: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.596: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.596: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.596: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.596: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.596: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.597: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.597: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.597: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.597: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.597: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.597: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.598: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.598: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.598: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.598: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.598: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.598: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.599: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.599: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.599: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.599: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.599: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.599: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.600: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.600: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.600: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.600: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.600: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.600: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.601: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.601: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.601: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.601: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.601: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.601: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.602: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.602: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.602: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.602: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.602: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.602: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.603: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.603: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.603: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.603: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.603: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.603: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.604: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.604: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.604: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.604: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.604: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.604: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.605: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.605: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.605: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.605: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.605: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.605: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.606: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.606: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.606: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.606: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.606: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.606: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.607: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.607: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.607: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.607: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.607: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.607: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.608: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.608: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.608: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.608: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.608: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.608: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.609: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.609: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.609: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.609: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.609: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.609: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.610: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.610: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.610: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.610: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.610: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.610: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.611: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.611: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.611: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.611: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.611: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.611: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.612: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.612: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.612: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.612: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.612: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.612: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.613: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.613: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.613: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.613: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.613: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.613: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.613: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.614: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.614: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.614: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.614: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.614: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.615: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.615: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.615: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.615: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.615: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.616: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.616: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.616: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.616: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.616: variance_after = 17 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.616: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.616: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.617: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.617: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.617: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.617: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.617: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.617: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.618: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.618: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.618: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.618: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.618: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.618: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.619: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.619: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.619: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.619: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.619: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.619: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.620: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.620: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.620: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.620: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.620: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.620: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.621: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.621: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.621: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.621: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.621: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.621: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.622: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.622: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.622: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.622: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.622: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.622: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.623: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.623: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.623: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.623: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.623: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.623: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.624: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.624: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.624: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.624: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.625: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.625: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.625: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.625: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.625: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.625: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.625: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.625: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.626: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.626: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.626: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.626: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.626: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.626: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.627: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.627: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.628: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.628: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.628: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.628: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.628: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.628: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.629: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.629: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.629: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.629: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.629: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.629: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.630: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.630: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.630: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.630: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.630: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.630: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.631: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.631: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.631: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.631: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.631: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.631: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.632: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.632: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.632: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.632: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.632: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.632: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.633: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.633: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.633: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.633: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.633: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.633: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.634: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.634: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.634: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.634: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.634: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.634: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.635: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.635: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.635: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.635: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.635: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.635: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.636: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.636: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.636: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.636: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.636: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.636: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.637: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.637: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.637: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.637: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.637: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.637: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.638: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.638: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.638: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.638: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.638: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.638: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.639: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.639: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.639: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.639: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.639: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.639: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.640: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.640: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.640: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.640: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.640: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.640: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.641: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.641: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.641: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.641: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.641: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.641: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.642: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.642: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.642: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.642: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.642: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.642: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.643: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.643: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.643: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.643: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.643: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.643: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.644: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.644: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.644: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.644: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.644: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.644: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.645: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.645: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.645: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.645: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.645: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.645: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.646: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.646: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.646: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.646: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.646: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.646: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.647: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.647: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.647: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.647: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.647: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.647: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.648: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.648: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.648: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.648: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.648: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.649: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.649: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.649: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.649: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.649: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.650: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.650: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.650: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.650: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.650: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.650: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.650: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.651: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.651: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.651: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.651: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.651: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.652: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.652: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.652: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.652: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.652: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.652: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.653: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.653: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.653: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.653: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.653: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.653: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.654: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.654: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.654: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.654: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.654: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.654: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.655: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.655: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.655: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.655: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.655: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.655: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.656: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.656: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.656: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.656: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.656: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.656: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.657: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.657: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.657: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.657: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.657: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.657: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.658: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.658: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.658: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.658: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.658: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.658: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.659: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.659: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.659: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.659: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.659: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.659: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.660: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.660: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.660: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.660: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.660: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.660: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.661: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.661: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.661: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.661: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.661: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.661: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.662: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.662: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.662: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.662: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.662: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.662: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.663: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.663: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.663: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.663: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.663: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.663: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.664: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.664: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.664: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.664: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.664: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.664: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.665: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.665: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.665: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.665: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.665: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.665: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.665: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.666: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.666: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.666: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.666: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.666: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.667: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.667: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.667: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.667: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.667: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.668: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.668: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.668: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.668: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.668: variance_after = 17 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.668: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.668: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.669: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.669: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.669: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.669: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.669: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.669: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.670: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.670: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.670: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.670: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.670: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.670: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.671: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.671: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.671: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.671: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.671: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.671: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.672: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.672: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.672: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.672: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.672: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.672: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.673: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.673: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.674: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.674: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.674: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.674: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.674: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.674: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.675: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.675: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.675: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.675: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.675: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.675: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.676: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.676: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.676: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.676: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.676: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.676: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.677: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.677: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.677: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.677: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.677: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.677: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.678: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.678: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.678: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.678: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.678: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.678: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.679: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.679: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.679: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.679: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.679: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.679: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.680: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.680: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.680: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.680: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.680: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.680: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.681: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.681: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.681: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.681: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.682: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.682: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.682: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.682: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.682: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.682: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.683: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.683: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.683: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.683: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.683: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.683: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.684: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.684: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.684: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.684: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.684: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.684: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.685: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.685: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.685: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.685: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.685: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.685: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.686: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.686: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.686: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.686: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.686: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.686: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.687: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.687: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.687: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.687: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.687: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.687: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.688: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.688: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.688: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.688: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.688: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.688: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.689: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.689: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.689: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.689: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.689: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.689: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.690: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.690: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.690: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.690: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.690: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.690: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.691: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.691: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.691: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.691: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.691: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.691: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.692: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.692: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.692: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.692: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.692: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.692: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.693: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.693: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.693: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.693: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.693: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.693: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.694: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.694: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.694: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.694: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.694: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.694: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.695: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.695: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.695: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.695: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.695: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.695: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.696: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.696: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.696: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.696: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.696: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.696: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.697: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.697: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.697: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.697: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.697: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.697: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.698: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.698: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.698: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.698: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.698: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.698: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.699: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.699: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.699: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.699: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.699: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.699: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.700: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.700: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.700: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.700: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.700: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.700: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.701: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.701: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.701: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.701: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.701: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.701: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.702: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.702: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.702: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.702: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.702: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.702: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.703: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.703: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.703: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.703: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.703: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.703: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.704: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.704: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.704: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.704: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.704: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.704: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.705: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.705: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.705: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.705: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.705: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.705: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.706: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.706: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.706: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.706: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.706: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.706: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.707: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.707: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.707: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.707: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.707: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.707: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.708: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.708: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.708: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.708: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.708: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.708: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.709: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.709: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.709: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.709: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.709: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.709: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.710: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.710: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.710: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.710: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.710: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.710: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.711: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.711: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.711: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.711: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.712: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.712: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.712: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.712: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.713: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.713: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.713: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.713: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.713: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.713: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.714: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.714: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.714: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.714: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.714: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.714: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.715: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.715: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.715: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.715: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.715: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.715: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.716: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.716: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.716: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.716: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.716: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.716: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.717: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.717: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.717: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.717: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.717: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.717: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.718: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.718: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.718: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.718: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.718: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.718: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.719: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.719: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.719: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.719: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.719: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.719: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.720: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.720: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.720: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.720: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.720: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.720: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.721: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.721: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.721: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.721: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.721: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.721: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.722: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.722: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.722: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.722: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.722: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.722: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.723: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.723: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.723: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.723: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.723: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.723: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.724: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.724: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.724: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.724: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.724: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.724: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.725: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.725: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.725: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.725: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.725: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.725: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.726: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.726: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.726: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.726: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.726: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.726: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.727: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.727: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.727: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.727: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.727: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.727: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.728: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.728: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.728: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.728: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.728: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.728: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.728: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.729: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.729: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.729: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.729: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.729: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.730: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.730: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.730: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.731: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.731: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.731: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.731: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.731: variance_after = 17 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.731: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.731: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.732: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.732: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.732: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.732: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.732: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.732: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.733: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.733: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.733: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.733: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.733: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.733: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.734: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.734: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.734: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.734: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.734: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.734: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.735: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.735: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.735: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.735: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.735: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.735: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.736: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.736: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.736: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.736: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.736: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.736: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.737: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.737: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.738: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.738: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.738: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.738: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.738: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.738: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.739: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.739: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.739: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.739: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.739: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.739: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.740: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.740: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.740: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.740: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.740: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.740: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.741: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.741: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.741: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.741: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.741: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.741: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.742: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.742: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.742: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.742: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.742: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.742: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.743: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.743: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.743: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.743: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.743: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.743: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.744: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.744: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.744: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.744: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.744: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.744: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.745: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.745: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.745: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.745: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.746: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.746: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.746: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.746: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.746: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.746: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.747: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.747: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.747: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.747: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.747: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.747: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.748: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.748: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.748: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.748: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.748: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.748: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.749: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.749: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.749: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.749: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.749: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.749: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.750: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.750: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.750: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.750: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.750: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.750: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.751: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.751: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.751: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.751: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.751: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.751: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.752: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.752: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.752: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.752: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.753: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.753: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.753: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.753: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.753: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.754: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.754: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.754: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.754: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.754: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.755: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.755: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.755: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.755: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.755: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.755: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.756: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.756: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.756: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.756: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.756: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.756: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.757: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.757: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.757: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.757: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.757: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.757: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.758: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.758: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.758: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.758: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.758: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.758: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.759: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.759: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.759: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.759: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.759: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.759: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.760: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.760: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.760: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.760: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.760: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.760: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.761: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.761: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.761: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.761: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.761: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.761: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.762: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.762: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.762: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.762: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.762: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.762: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.763: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.763: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.763: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.763: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.763: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.763: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.764: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.764: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.764: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.764: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.764: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.764: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.765: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.765: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.765: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.765: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.765: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.765: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.766: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.766: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.766: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.766: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.766: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.766: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.767: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.767: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.767: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.767: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.767: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.767: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.768: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.768: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.768: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.768: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.769: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.769: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.769: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.769: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.769: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.769: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.770: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.770: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.770: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.770: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.770: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.770: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.771: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.771: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.771: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.771: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.771: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.771: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.772: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.772: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.772: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.772: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.772: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.772: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.773: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.773: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.773: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.773: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.773: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.773: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.774: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.774: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.774: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.774: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.774: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.774: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.775: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.775: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.775: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.775: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.775: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.775: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.776: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.776: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.776: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.776: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.776: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.776: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.777: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.777: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.777: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.777: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.777: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.777: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.778: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.778: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.779: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.779: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.779: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.779: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.779: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.779: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.780: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.780: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.780: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.780: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.780: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.780: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.781: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.781: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.781: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.781: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.781: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.781: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.782: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.782: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.782: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.782: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.782: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.782: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.783: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.783: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.783: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.783: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.783: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.783: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.784: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.784: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.784: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.784: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.784: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.784: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.785: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.785: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.785: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.785: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.785: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.785: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.786: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.786: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.786: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.786: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.786: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.786: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.787: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.787: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.787: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.787: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.787: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.787: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.788: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.788: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.788: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.788: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.788: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.788: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.789: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.789: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.789: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.789: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.789: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.789: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.790: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.790: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.790: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.790: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.790: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.790: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.791: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.791: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.791: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.791: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.791: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.791: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.792: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.792: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.792: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.792: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.792: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.792: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.793: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.793: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.793: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.793: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.793: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.793: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.794: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.794: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.794: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.794: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.794: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.794: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.795: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.795: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.795: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.795: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.795: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.795: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.796: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.796: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.796: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.796: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.796: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.796: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.797: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.797: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.797: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.797: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.797: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.797: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.798: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.798: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.798: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.798: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.798: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.798: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.799: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.799: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.799: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.799: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.799: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.799: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.800: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.800: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.800: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.800: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.800: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.800: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.801: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.801: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.801: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.801: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.801: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.801: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.802: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.802: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.802: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.802: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.802: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.802: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.803: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.803: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.803: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.803: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.803: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.803: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.804: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.804: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.804: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.804: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.804: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.804: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.805: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.805: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.805: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.805: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.805: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.805: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.806: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.806: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.806: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.806: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.806: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.806: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.807: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.807: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.807: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.807: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.807: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.807: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.808: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.808: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.808: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.808: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.808: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.808: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.809: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.809: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.809: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.809: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.809: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.809: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.810: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.810: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.810: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.810: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.810: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.810: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.811: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.811: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.811: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.811: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.812: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.812: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.812: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.812: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.812: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.812: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.813: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.813: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.813: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.813: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.813: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.813: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.814: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.814: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.814: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.814: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.814: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.814: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.815: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.815: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.815: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.815: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.815: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.815: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.816: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.816: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.816: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.816: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.816: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.816: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.817: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.817: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.817: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.817: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.817: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.817: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.818: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.818: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.818: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.818: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.818: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.818: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.819: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.819: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.819: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.819: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.819: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.819: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.820: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.820: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.820: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.820: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.820: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.820: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.821: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.821: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.821: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.821: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.821: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.821: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.822: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.822: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.822: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.822: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.822: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.822: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.823: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.823: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.823: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.823: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.823: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.823: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.824: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.824: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.824: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.824: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.824: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.824: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.825: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.825: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.825: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.825: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.825: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.825: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.826: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.826: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.826: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.826: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.826: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.826: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.827: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.827: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.827: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.827: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.827: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.827: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.828: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.828: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.829: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.829: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.829: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.829: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.829: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.829: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.830: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.830: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.830: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.830: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.830: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.830: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.831: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.831: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.831: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.831: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.831: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.831: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.832: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.832: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.832: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.832: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.833: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.833: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.833: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.833: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.833: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.833: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.834: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.834: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.834: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.834: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.834: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.834: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.835: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.835: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.835: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.835: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.835: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.835: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.836: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.836: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.836: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.836: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.836: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.836: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.837: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.837: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.837: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.837: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.837: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.837: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.838: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.838: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.838: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.838: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.838: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.838: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.839: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.839: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.840: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.840: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.840: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.840: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.840: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.840: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.841: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.841: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.841: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.841: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.841: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.841: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.842: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.842: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.842: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.842: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.842: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.842: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.843: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.843: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.843: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.843: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.843: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.843: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.844: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.844: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.844: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.844: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.844: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.844: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.845: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.845: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.845: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.845: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.845: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.845: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.846: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.846: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.846: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.846: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.846: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.846: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.847: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.847: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.847: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.847: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.847: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.847: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.848: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.848: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.848: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.848: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.848: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.848: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.849: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.849: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.849: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.849: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.849: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.849: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.850: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.850: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.850: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.850: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.850: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.850: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.851: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.851: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.851: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.851: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.851: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.851: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.852: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.852: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.852: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.852: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.852: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.852: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.853: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.853: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.853: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.853: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.853: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.853: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.854: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.854: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.854: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.854: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.854: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.854: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.855: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.855: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.855: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.855: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.855: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.855: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.856: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.856: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.856: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.856: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.857: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.857: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.857: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.857: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.857: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.857: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.858: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.858: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.858: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.858: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.858: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.858: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.859: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.859: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.859: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.859: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.859: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.859: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.860: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.860: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.860: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.860: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.860: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.860: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.861: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.861: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.861: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.861: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.861: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.861: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.862: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.862: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.862: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.862: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.862: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.862: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.863: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.863: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.863: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.863: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.863: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.863: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.864: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.864: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.864: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.864: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.864: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.864: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.865: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.865: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.865: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.865: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.865: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.865: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.866: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.866: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.866: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.866: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.866: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.866: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.867: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.867: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.867: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.867: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.867: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.867: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.868: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.868: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.868: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.868: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.868: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.868: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.869: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.869: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.869: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.869: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.869: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.869: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.870: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.870: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.870: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.870: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.870: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.870: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.871: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.871: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.871: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.871: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.871: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.871: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.872: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.872: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.872: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.872: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.872: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.872: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.873: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.873: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.873: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.873: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.873: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.873: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.874: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.874: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.875: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.875: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.875: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.875: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.875: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.875: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.876: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.876: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.876: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.876: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.876: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.876: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.877: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.877: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.877: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.877: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.877: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.877: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.878: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.878: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.878: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.878: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.878: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.878: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.879: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.879: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.879: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.879: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.880: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.880: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.880: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.880: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.880: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.880: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.881: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.881: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.881: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.881: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.881: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.881: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.882: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.882: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.882: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.882: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.882: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.882: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.883: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.883: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.883: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.883: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.883: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.883: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.884: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.884: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.884: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.884: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.884: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.884: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.884: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.885: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.885: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.885: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.885: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.885: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.886: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.886: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.887: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.887: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.887: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.887: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.887: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.888: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.888: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.888: variance_after = 20 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.888: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.888: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.888: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.888: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.889: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.889: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.889: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.889: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.890: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.890: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.890: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.890: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.890: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.890: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.891: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.891: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.891: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.891: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.891: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.891: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.892: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.892: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.892: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.892: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.892: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.892: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.893: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.893: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.893: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.893: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.893: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.893: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.894: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.894: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.894: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.894: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.894: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.894: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.895: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.895: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.895: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.895: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.895: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.895: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.896: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.896: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.896: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.896: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.896: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.896: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.897: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.897: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.897: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.897: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.897: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.897: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.898: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.898: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.898: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.898: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.898: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.898: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.899: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.899: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.899: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.899: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.899: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.899: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.900: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.900: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.900: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.900: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.900: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.900: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.901: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.901: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.901: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.901: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.901: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.901: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.902: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.902: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.902: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.902: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.902: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.902: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.903: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.903: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.903: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.903: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.903: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.903: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.904: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.904: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.904: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.904: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.905: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.905: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.905: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.905: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.905: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.905: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.906: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.906: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.906: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.906: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.907: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.907: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.907: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.907: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.907: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.907: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.908: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.908: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.908: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.908: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.908: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.908: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.909: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.909: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.909: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.909: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.909: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.909: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.910: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.910: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.910: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.910: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.910: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.910: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.911: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.911: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.911: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.911: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.911: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.911: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.912: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.912: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.912: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.912: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.912: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.912: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.913: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.913: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.913: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.913: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.913: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.913: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.914: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.914: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.914: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.914: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.914: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.914: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.915: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.915: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.915: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.915: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.915: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.915: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.916: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.916: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.916: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.916: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.916: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.916: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.917: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.917: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.917: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.917: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.917: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.917: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.918: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.918: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.918: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.918: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.918: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.918: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.919: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.919: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.919: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.919: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.919: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.919: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.920: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.920: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.920: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.920: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.920: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.920: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.921: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.921: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.921: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.921: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.922: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.922: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.922: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.922: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.922: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.922: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.923: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.923: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.923: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.923: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.923: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.923: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.924: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.924: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.924: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.924: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.924: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.924: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.925: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.925: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.925: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.925: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.925: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.925: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.926: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.926: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.926: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.926: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.926: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.926: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.927: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.927: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.927: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.927: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.927: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.927: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.928: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.928: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.929: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.929: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.929: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.929: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.929: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.929: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.930: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.930: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.930: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.930: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.930: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.930: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.931: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.931: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.931: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.931: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.931: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.931: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.932: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.932: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.932: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.932: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.932: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.932: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.933: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.933: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.933: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.933: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.933: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.933: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.934: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.934: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.934: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.934: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.934: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.934: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.935: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.935: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.935: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.935: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.935: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.935: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.936: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.936: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.936: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.936: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.937: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.937: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.937: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.937: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.937: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.937: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.938: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.938: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.938: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.938: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.938: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.938: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.939: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.939: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.939: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.939: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.939: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.939: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.940: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.940: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.940: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.940: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.940: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.940: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.941: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.941: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.941: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.941: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.941: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.941: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.942: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.942: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.942: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.942: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.942: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.942: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.943: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.943: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.943: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.943: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.943: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.943: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.944: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.944: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.944: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.944: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.944: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.944: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.945: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.945: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.945: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.945: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.945: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.945: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.946: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.946: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.946: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.946: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.946: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.946: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.947: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.947: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.947: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.947: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.947: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.947: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.948: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.948: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.948: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.948: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.948: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.949: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.949: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.949: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.950: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.950: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.950: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.950: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.950: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.950: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.951: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.951: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.951: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.951: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.951: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.951: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.952: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.952: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.952: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.952: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.952: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.952: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.953: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.953: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.953: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.953: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.953: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.953: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.954: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.954: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.954: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.954: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.954: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.954: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.955: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.955: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.955: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.955: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.955: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.955: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.956: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.956: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.956: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.956: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.956: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.956: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.957: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.957: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.957: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.957: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.957: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.957: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.958: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.958: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.958: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.958: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.958: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.958: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.959: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.959: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.959: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.959: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.959: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.959: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.960: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.960: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.960: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.960: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.960: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.960: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.961: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.961: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.961: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.961: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.961: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.961: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.962: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.962: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.962: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.962: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.962: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.962: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.963: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.963: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.963: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.963: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.963: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.963: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.964: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.964: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.964: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.964: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.964: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.964: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.965: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.965: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.965: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.965: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.965: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.965: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.966: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.966: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.966: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.966: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.966: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.966: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.966: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.967: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.967: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.967: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.967: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.967: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.968: [vfs7552] CAPTURE_NUM_STATES entering state 2 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.968: [vfs7552] REQUEST CHUNK entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.968: Sending vfs7552_read_image_chunk 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.968: [vfs7552] REQUEST CHUNK completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.968: [vfs7552] CAPTURE_NUM_STATES entering state 3 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.969: [vfs7552] CAPTURE_NUM_STATES entering state 4 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.969: Cleaning image 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.969: variance_after = 17 430s 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.969: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.969: Sending vfs7552_is_image_ready 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.969: [vfs7552] QUERY DATA READY entering state 1 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.969: Receiving 64 bytes 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.970: Got 6 bytes out of 64 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.970: [vfs7552] QUERY DATA READY completed successfully 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 430s (process:2196): libfprint-SSM-DEBUG: 05:09:10.970: [vfs7552] QUERY DATA READY entering state 0 430s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.970: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.970: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.970: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.971: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.971: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.971: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.971: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.971: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.971: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.972: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.972: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.972: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.972: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.972: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.972: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.973: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.973: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.973: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.973: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.973: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.973: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.974: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.974: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.974: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.974: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.974: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.974: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.975: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.975: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.975: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.975: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.975: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.975: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.976: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.976: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.976: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.976: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.976: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.976: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.977: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.977: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.977: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.977: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.977: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.977: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.978: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.978: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.978: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.978: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.978: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.978: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.979: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.979: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.979: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.979: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.979: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.979: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.980: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.980: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.980: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.980: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.980: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.980: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.981: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.981: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.981: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.981: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.981: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.981: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.982: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.982: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.982: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.982: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.982: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.982: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.983: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.983: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.983: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.983: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.983: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.984: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.984: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.984: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.984: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.984: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.984: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.985: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.985: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.985: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.985: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.985: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.986: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.986: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.986: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.986: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.986: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.986: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.987: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.987: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.987: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.987: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.987: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.987: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.988: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.988: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.988: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.988: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.988: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.988: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.989: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.989: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.989: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.989: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.989: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.989: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.990: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.990: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.990: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.990: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.990: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.990: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.991: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.991: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.991: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.991: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.991: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.991: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.992: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.992: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.992: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.992: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.992: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.992: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.993: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.993: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.993: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.993: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.993: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.993: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.994: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.994: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.994: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.994: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.994: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.994: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.995: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.995: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.995: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.995: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.995: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.995: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.996: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.996: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.996: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.996: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.996: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.996: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.997: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.997: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.997: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.997: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.997: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.997: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.998: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.998: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.998: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.998: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.998: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.998: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.999: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.999: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.999: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.999: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:10.999: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:10.999: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.000: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.000: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.000: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.000: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.000: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.000: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.001: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.001: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.001: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.001: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.001: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.001: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.002: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.002: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.002: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.002: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.002: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.002: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.003: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.003: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.003: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.003: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.003: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.003: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.004: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.004: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.004: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.004: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.004: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.004: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.005: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.005: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.005: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.005: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.005: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.005: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.006: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.006: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.006: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.006: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.006: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.006: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.007: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.007: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.007: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.007: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.007: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.007: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.008: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.008: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.009: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.009: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.009: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.009: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.009: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.009: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.010: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.010: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.010: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.010: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.010: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.010: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.011: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.011: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.011: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.011: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.011: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.011: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.012: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.012: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.012: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.012: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.012: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.012: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.013: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.013: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.013: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.013: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.013: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.013: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.014: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.014: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.014: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.014: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.014: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.014: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.015: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.015: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.015: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.015: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.015: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.015: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.016: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.016: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.016: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.016: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.016: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.016: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.017: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.017: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.017: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.017: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.017: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.017: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.018: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.018: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.018: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.018: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.018: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.018: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.019: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.019: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.019: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.019: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.019: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.019: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.019: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.020: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.020: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.020: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.020: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.020: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.021: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.021: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.021: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.021: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.021: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.022: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.022: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.022: variance_after = 17 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.022: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.022: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.022: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.022: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.023: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.023: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.023: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.023: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.023: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.023: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.024: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.024: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.024: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.024: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.024: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.024: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.025: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.025: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.025: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.025: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.025: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.025: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.026: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.026: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.026: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.026: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.026: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.026: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.027: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.027: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.027: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.027: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.028: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.028: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.028: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.028: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.028: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.028: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.029: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.029: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.029: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.029: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.029: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.029: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.030: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.030: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.030: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.030: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.030: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.030: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.031: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.031: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.031: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.031: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.031: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.031: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.032: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.032: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.032: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.032: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.032: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.032: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.033: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.033: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.033: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.033: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.033: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.033: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.034: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.034: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.034: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.034: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.034: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.034: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.035: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.035: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.035: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.035: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.035: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.036: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.036: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.036: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.036: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.036: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.036: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.036: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.037: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.037: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.037: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.037: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.038: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.038: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.038: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.038: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.038: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.039: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.039: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.039: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.039: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.039: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.040: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.040: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.040: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.040: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.040: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.040: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.041: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.041: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.041: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.041: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.041: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.041: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.042: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.042: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.042: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.042: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.042: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.042: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.043: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.043: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.043: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.043: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.043: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.043: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.044: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.044: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.044: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.044: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.044: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.044: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.045: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.045: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.045: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.045: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.045: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.045: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.046: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.046: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.046: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.046: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.046: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.046: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.047: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.047: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.047: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.047: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.047: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.047: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.048: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.048: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.048: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.048: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.048: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.048: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.049: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.049: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.049: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.049: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.049: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.049: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.050: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.050: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.050: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.050: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.050: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.050: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.051: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.051: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.051: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.051: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.051: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.051: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.052: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.052: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.052: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.052: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.052: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.052: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.053: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.053: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.053: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.053: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.053: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.053: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.054: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.054: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.054: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.054: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.054: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.054: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.055: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.055: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.055: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.055: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.055: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.055: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.056: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.056: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.056: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.056: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.056: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.056: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.057: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.057: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.057: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.057: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.057: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.057: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.058: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.058: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.058: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.058: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.058: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.059: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.059: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.059: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.059: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.059: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.060: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.060: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.060: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.060: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.060: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.060: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.061: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.061: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.061: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.061: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.061: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.061: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.062: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.062: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.062: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.062: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.062: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.062: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.063: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.063: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.063: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.063: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.063: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.063: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.064: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.064: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.064: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.064: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.064: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.064: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.065: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.065: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.065: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.065: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.065: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.065: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.066: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.066: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.066: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.066: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.066: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.066: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.067: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.067: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.067: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.067: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.067: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.067: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.068: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.068: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.068: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.068: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.068: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.068: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.069: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.069: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.069: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.069: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.069: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.069: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.069: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.070: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.070: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.071: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.071: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.071: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.071: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.071: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.072: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.072: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.072: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.072: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.072: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.073: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.073: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.073: variance_after = 17 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.073: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.073: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.073: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.073: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.074: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.074: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.074: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.074: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.074: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.074: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.075: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.075: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.075: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.075: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.075: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.075: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.076: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.076: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.076: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.076: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.076: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.076: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.077: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.077: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.077: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.077: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.077: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.077: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.078: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.078: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.078: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.078: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.078: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.078: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.079: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.079: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.079: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.079: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.079: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.079: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.080: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.080: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.080: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.080: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.080: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.080: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.081: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.081: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.081: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.081: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.081: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.082: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.082: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.082: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.082: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.082: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.083: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.083: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.083: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.083: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.083: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.083: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.084: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.084: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.084: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.084: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.084: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.084: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.085: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.085: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.085: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.085: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.085: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.085: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.086: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.086: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.086: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.086: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.086: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.086: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.087: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.087: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.087: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.087: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.087: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.087: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.088: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.088: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.088: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.088: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.088: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.088: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.089: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.089: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.089: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.089: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.089: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.089: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.090: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.090: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.090: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.090: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.090: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.090: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.091: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.091: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.091: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.091: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.091: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.091: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.092: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.092: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.092: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.092: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.092: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.092: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.093: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.093: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.093: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.093: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.093: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.093: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.094: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.094: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.094: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.094: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.094: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.094: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.095: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.095: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.095: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.095: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.095: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.095: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.096: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.096: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.096: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.096: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.096: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.096: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.097: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.097: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.097: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.097: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.097: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.097: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.098: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.098: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.098: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.098: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.098: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.098: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.099: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.099: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.100: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.100: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.100: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.100: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.100: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.100: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.101: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.101: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.101: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.101: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.101: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.101: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.102: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.102: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.102: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.102: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.102: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.102: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.103: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.103: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.103: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.103: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.103: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.103: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.104: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.104: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.104: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.104: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.104: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.104: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.105: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.105: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.105: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.105: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.105: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.105: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.106: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.106: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.106: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.106: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.106: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.106: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.107: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.107: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.107: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.107: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.108: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.108: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.108: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.108: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.108: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.108: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.109: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.109: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.109: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.109: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.109: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.109: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.110: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.110: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.110: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.110: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.110: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.110: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.111: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.111: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.111: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.111: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.112: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.112: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.112: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.112: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.112: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.112: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.112: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.113: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.113: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.113: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.113: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.113: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.114: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.114: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.114: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.114: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.115: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.115: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.115: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.115: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.115: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.115: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.116: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.116: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.116: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.116: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.116: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.116: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.116: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.117: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.117: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.117: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.117: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.117: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.118: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.118: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.118: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.118: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.118: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.119: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.119: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.119: variance_after = 17 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.119: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.119: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.120: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.120: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.120: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.120: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.120: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.120: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.121: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.121: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.121: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.121: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.121: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.121: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.122: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.122: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.122: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.122: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.122: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.122: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.123: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.123: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.123: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.123: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.123: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.123: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.124: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.124: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.124: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.124: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.124: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.124: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.125: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.125: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.125: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.125: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.125: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.125: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.126: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.126: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.126: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.126: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.126: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.126: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.127: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.127: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.127: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.127: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.127: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.127: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.128: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.128: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.128: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.128: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.128: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.128: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.129: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.129: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.129: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.129: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.129: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.129: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.130: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.130: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.130: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.130: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.130: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.130: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.131: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.131: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.131: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.131: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.131: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.131: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.132: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.132: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.132: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.132: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.132: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.132: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.133: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.133: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.133: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.133: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.133: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.133: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.134: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.134: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.134: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.134: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.134: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.134: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.135: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.135: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.135: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.135: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.135: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.135: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.136: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.136: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.136: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.136: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.136: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.136: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.137: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.137: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.137: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.137: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.137: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.137: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.138: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.138: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.138: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.138: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.138: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.138: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.139: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.139: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.140: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.140: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.140: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.140: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.140: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.140: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.141: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.141: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.141: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.141: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.141: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.141: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.142: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.142: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.142: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.142: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.142: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.142: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.143: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.143: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.143: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.143: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.143: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.143: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.144: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.144: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.144: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.144: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.144: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.144: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.145: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.145: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.145: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.145: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.145: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.145: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.146: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.146: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.146: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.146: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.146: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.146: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.147: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.147: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.147: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.147: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.147: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.147: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.148: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.148: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.148: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.148: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.148: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.148: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.149: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.149: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.149: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.149: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.149: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.149: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.150: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.150: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.150: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.150: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.150: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.150: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.151: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.151: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.151: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.151: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.151: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.151: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.152: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.152: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.152: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.152: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.152: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.152: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.153: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.153: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.153: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.153: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.153: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.153: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.154: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.154: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.154: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.154: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.154: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.154: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.155: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.155: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.155: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.155: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.155: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.155: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.156: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.156: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.156: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.156: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.157: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.157: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.157: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.157: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.157: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.157: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.158: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.158: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.158: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.158: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.158: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.158: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.159: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.159: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.159: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.159: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.159: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.159: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.160: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.160: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.160: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.160: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.160: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.160: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.161: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.161: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.161: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.161: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.162: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.162: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.162: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.162: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.163: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.163: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.163: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.163: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.163: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.163: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.164: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.164: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.164: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.164: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.164: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.164: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.165: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.165: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.165: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.165: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.165: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.165: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.166: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.166: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.166: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.166: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.166: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.166: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.166: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.167: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.167: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.167: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.167: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.167: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.168: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.168: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.168: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.168: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.168: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.169: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.169: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.169: variance_after = 16 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.169: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.169: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.169: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.169: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.170: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.170: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.170: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.170: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.170: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.170: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.171: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.171: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.171: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.171: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.172: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.172: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.172: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.172: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.172: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.172: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.173: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.173: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.173: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.173: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.173: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.173: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.174: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.174: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.174: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.174: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.174: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.174: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.175: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.175: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.175: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.175: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.175: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.175: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.176: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.176: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.176: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.176: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.176: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.176: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.177: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.177: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.177: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.177: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.177: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.177: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.178: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.178: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.178: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.178: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.178: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.178: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.179: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.179: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.179: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.179: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.179: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.179: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.180: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.180: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.180: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.180: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.180: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.180: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.181: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.181: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.181: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.181: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.181: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.181: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.182: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.182: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.182: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.182: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.182: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.182: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.183: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.183: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.183: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.183: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.183: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.183: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.184: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.184: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.184: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.184: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.184: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.184: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.185: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.185: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.185: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.185: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.185: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.185: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.186: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.186: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.186: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.186: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.186: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.186: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.187: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.187: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.187: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.187: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.187: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.187: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.188: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.188: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.188: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.188: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.188: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.188: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.189: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.189: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.189: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.189: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.189: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.189: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.190: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.190: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.190: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.190: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.190: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.190: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.191: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.191: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.191: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.191: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.191: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.191: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.192: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.192: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.192: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.192: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.192: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.192: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.193: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.193: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.193: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.193: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.193: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.193: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.194: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.194: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.194: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.194: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.194: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.194: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.195: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.195: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.195: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.195: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.195: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.195: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.196: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.196: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.196: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.196: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.196: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.196: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.197: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.197: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.197: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.198: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.198: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.198: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.198: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.198: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.199: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.199: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.199: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.199: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.199: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.199: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.200: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.200: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.200: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.200: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.200: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.200: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.201: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.201: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.201: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.201: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.201: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.201: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.202: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.202: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.202: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.202: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.202: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.202: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.203: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.203: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.203: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.203: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.203: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.203: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.204: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.204: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.204: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.204: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.204: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.204: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.205: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.205: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.205: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.205: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.205: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.205: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.206: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.206: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.206: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.206: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.206: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.206: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.207: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.207: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.207: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.207: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.207: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.207: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.208: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.208: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.208: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.208: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.208: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.208: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.209: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.209: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.209: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.209: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.209: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.209: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.210: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.210: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.210: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.210: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.210: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.210: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.211: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.211: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.211: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.211: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.211: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.211: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.212: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.212: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.212: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.212: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.212: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.212: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.213: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.213: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.213: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.213: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.213: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.213: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.214: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.214: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.214: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.214: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.214: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.214: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.215: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.215: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.215: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.215: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.216: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.216: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.216: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.216: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.216: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.217: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.217: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.217: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.217: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.217: variance_after = 17 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.217: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.217: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.218: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.218: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.218: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.218: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.218: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.218: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.219: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.219: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.219: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.220: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.220: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.220: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.220: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.220: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.221: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.221: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.221: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.221: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.221: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.221: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.222: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.222: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.222: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.222: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.222: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.222: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.223: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.223: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.223: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.223: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.223: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.223: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.224: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.224: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.224: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.224: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.224: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.224: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.225: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.225: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.225: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.225: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.225: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.225: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.226: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.226: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.226: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.226: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.226: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.226: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.227: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.227: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.227: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.227: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.227: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.227: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.228: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.228: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.228: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.228: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.229: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.229: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.229: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.229: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.229: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.229: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.230: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.230: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.230: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.230: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.230: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.230: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.231: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.231: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.231: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.231: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.231: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.231: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.232: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.232: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.232: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.232: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.232: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.232: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.233: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.233: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.233: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.233: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.233: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.233: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.234: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.234: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.234: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.234: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.234: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.234: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.235: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.235: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.235: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.235: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.235: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.235: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.236: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.236: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.236: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.236: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.236: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.236: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.237: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.237: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.237: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.237: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.237: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.238: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.238: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.238: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.239: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.239: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.239: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.239: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.239: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.239: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.240: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.240: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.240: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.240: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.240: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.240: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.240: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.241: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.241: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.241: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.241: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.241: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.241: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.242: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.242: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.242: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.242: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.242: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.243: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.243: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.243: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.243: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.243: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.243: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.244: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.244: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.244: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.244: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.244: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.244: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.245: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.245: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.245: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.245: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.245: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.245: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.246: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.246: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.246: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.246: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.246: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.246: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.247: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.247: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.247: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.247: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.247: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.247: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.248: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.248: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.248: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.248: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.248: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.248: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.249: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.249: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.249: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.249: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.249: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.249: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.250: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.250: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.250: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.250: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.250: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.250: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.251: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.251: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.251: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.251: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.251: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.251: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.252: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.252: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.252: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.252: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.252: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.252: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.253: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.253: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.253: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.253: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.253: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.253: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.254: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.254: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.254: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.254: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.254: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.254: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.255: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.255: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.255: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.255: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.255: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.255: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.256: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.256: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.256: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.256: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.256: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.256: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.257: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.257: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.257: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.257: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.257: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.257: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.258: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.258: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.258: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.258: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.258: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.258: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.259: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.259: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.259: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.259: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.259: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.259: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.260: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.260: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.260: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.260: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.260: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.260: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.260: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.261: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.261: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.261: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.261: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.261: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.262: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.262: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.262: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.262: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.262: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.263: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.263: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.263: variance_after = 16 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.263: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.263: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.264: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.264: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.264: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.264: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.264: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.264: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.265: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.265: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.265: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.265: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.265: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.265: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.266: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.266: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.266: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.266: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.266: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.266: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.267: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.267: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.267: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.267: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.267: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.267: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.268: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.268: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.268: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.268: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.268: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.268: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.269: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.269: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.269: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.269: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.269: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.269: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.270: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.270: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.270: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.270: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.270: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.270: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.271: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.271: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.271: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.271: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.271: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.271: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.272: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.272: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.272: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.272: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.273: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.273: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.273: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.273: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.274: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.274: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.274: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.274: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.274: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.274: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.275: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.275: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.275: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.275: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.275: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.275: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.276: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.276: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.276: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.276: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.276: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.276: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.277: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.277: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.277: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.277: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.277: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.277: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.278: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.278: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.278: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.278: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.278: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.278: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.279: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.279: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.279: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.279: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.280: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.280: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.280: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.280: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.280: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.280: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.281: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.281: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.281: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.281: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.281: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.281: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.282: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.282: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.282: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.282: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.282: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.282: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.283: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.283: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.283: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.283: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.283: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.283: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.284: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.284: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.284: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.284: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.284: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.284: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.285: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.285: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.285: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.285: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.285: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.285: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.286: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.286: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.286: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.286: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.286: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.286: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.287: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.287: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.287: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.287: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.287: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.287: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.288: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.288: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.288: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.288: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.288: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.288: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.289: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.289: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.289: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.289: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.289: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.289: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.290: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.290: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.290: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.290: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.290: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.290: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.291: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.291: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.291: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.291: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.291: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.291: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.292: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.292: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.293: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.293: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.293: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.293: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.293: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.293: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.294: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.294: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.294: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.294: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.294: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.294: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.295: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.295: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.295: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.295: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.295: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.295: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.296: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.296: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.296: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.296: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.296: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.296: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.297: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.297: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.297: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.297: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.297: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.297: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.298: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.298: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.298: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.298: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.298: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.298: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.299: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.299: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.299: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.299: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.299: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.299: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.300: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.300: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.300: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.300: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.300: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.300: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.301: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.301: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.301: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.301: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.301: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.301: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.302: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.302: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.302: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.302: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.302: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.302: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.303: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.303: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.303: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.303: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.303: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.303: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.304: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.304: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.304: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.304: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.304: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.304: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.305: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.305: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.305: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.305: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.305: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.305: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.306: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.306: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.306: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.306: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.306: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.306: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.306: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.307: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.307: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.307: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.307: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.307: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.308: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.308: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.308: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.308: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.308: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.309: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.309: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.309: variance_after = 2168 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.309: [vfs7552] CAPTURE_NUM_STATES completed successfully 431s (process:2196): libfprint-device-DEBUG: 05:09:11.309: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 431s (process:2196): libfprint-image_device-DEBUG: 05:09:11.309: Image device reported finger status: on 431s (process:2196): libfprint-image_device-DEBUG: 05:09:11.309: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.359: changing to 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.359: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.359: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.360: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.360: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.360: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.360: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.360: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.360: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.360: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.361: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.361: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.361: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.361: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.361: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.362: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.362: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.362: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.362: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.362: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.363: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.363: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.363: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.363: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.363: variance_after = 2082 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.363: [vfs7552] CAPTURE_NUM_STATES completed successfully 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.363: Image captured 431s (process:2196): libfprint-image_device-DEBUG: 05:09:11.364: Image device captured an image 431s (process:2196): libfprint-image_device-DEBUG: 05:09:11.365: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 431s (process:2196): libfprint-device-DEBUG: 05:09:11.365: Device reported finger status change: FP_FINGER_STATUS_PRESENT 431s (process:2196): libfprint-image-DEBUG: 05:09:11.384: Minutiae scan completed in 0.019315 secs 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.413: changing to 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.413: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.413: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.414: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.414: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.415: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.415: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.415: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.415: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.415: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.415: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.415: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.416: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.416: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.416: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.416: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.416: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.417: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.417: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.417: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.417: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.417: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.418: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.418: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.418: variance_after = 2003 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.418: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.418: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.418: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.418: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.419: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.419: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.419: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.419: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.419: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.419: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.420: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.420: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.420: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.420: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.420: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.420: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.421: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.421: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.421: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.421: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.421: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.421: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.422: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.422: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.422: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.422: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.422: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.422: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.423: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.423: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.423: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.423: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.423: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.423: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.424: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.424: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.424: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.424: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.425: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.425: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.425: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.425: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.425: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.425: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.426: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.426: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.426: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.426: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.426: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.426: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.427: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.427: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.427: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.427: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.427: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.427: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.428: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.428: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.428: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.428: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.428: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.428: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.429: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.429: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.429: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.429: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.429: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.429: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.430: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.430: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.430: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.431: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.431: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.431: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.431: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.431: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.432: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.432: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.432: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.432: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.432: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.432: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.433: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.433: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.433: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.433: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.433: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.433: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.434: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.434: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.434: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.434: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.434: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.434: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.435: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.435: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.435: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.435: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.435: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.435: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.436: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.436: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.436: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.436: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.436: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.436: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.437: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.437: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.437: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.437: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.437: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.437: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.438: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.438: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.438: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.438: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.438: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.438: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.439: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.439: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.439: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.439: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.439: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.439: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.440: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.440: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.440: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.440: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.440: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.440: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.441: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.441: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.441: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.441: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.441: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.441: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.442: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.442: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.442: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.442: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.443: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.443: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.443: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.443: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.443: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.443: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.444: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.444: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.444: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.444: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.444: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.444: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.445: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.445: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.445: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.445: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.445: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.445: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.446: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.446: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.446: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.446: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.446: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.446: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.447: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.447: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.447: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.447: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.447: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.447: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.448: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.448: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.448: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.448: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.448: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.448: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.449: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.449: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.449: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.449: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.449: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.449: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.450: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.450: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.450: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.450: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.450: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.450: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.451: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.451: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.451: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.451: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.451: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.452: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.452: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.452: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.453: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.453: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.453: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.453: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.453: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.453: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.454: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.454: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.454: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.454: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.454: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.454: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.455: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.455: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.455: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.455: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.455: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.455: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.456: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.456: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.456: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.456: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.456: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.456: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.457: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.457: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.457: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.457: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.457: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.457: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.458: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.458: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.458: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.458: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.458: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.458: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.459: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.459: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.459: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.459: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.459: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.459: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.460: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.460: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.460: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.460: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.460: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.460: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.461: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.461: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.461: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.461: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.461: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.461: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.462: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.462: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.462: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.462: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.462: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.462: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.463: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.463: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.463: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.463: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.463: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.463: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.464: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.464: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.464: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.464: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.464: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.464: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.465: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.465: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.465: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.465: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.465: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.465: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.466: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.466: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.466: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.466: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.467: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.467: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.467: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.467: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.467: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.467: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.468: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.468: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.468: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.468: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.468: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.468: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.469: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.469: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.469: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.469: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.469: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.469: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.470: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.470: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.470: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.470: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.470: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.470: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.471: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.471: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.471: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.471: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.471: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.471: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.472: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.472: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.472: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.472: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.472: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.472: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.473: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.473: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.473: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.473: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.473: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.473: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.474: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.474: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.474: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.474: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.474: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.474: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.475: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.475: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.475: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.475: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.475: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.475: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.476: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.476: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.477: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.477: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.477: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.477: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.477: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.477: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.478: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.478: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.478: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.478: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.478: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.478: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.479: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.479: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.479: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.479: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.479: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.479: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.480: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.480: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.480: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.480: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.480: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.480: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.481: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.481: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.481: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.481: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.481: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.481: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.482: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.482: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.482: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.482: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.482: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.482: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.483: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.483: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.483: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.483: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.483: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.483: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.484: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.484: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.484: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.484: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.485: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.485: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.485: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.485: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.485: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.485: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.486: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.486: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.486: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.486: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.486: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.486: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.487: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.487: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.487: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.487: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.487: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.487: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.488: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.488: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.488: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.488: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.488: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.488: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.489: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.489: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.489: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.489: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.489: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.489: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.490: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.490: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.490: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.490: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.490: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.490: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.491: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.491: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.491: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.491: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.491: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.491: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.492: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.492: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.493: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.493: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.493: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.493: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.493: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.493: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.494: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.494: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.494: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.494: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.494: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.494: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.495: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.495: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.495: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.495: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.495: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.495: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.496: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.496: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.496: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.496: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.496: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.496: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.497: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.497: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.497: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.497: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.497: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.497: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.498: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.498: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.498: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.498: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.499: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.499: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.499: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.499: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.499: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.499: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.500: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.500: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.500: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.500: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.500: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.500: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.501: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.501: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.501: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.501: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.501: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.501: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.502: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.502: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.502: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.502: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.502: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.502: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.503: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.503: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.503: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.503: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.503: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.503: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.504: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.504: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.504: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.504: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.504: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.504: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.505: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.505: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.505: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.505: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.505: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.505: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.506: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.506: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.506: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.506: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.506: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.506: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.507: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.507: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.507: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.507: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.507: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.507: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.508: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.508: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.508: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.508: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.508: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.508: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.509: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.509: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.509: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.509: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.509: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.509: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.510: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.510: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.511: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.511: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.511: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.511: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.511: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.511: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.512: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.512: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.512: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.512: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.512: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.512: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.513: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.513: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.513: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.513: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.513: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.513: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.514: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.514: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.514: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.514: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.514: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.514: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.515: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.515: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.515: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.515: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.515: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.515: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.516: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.516: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.516: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.516: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.516: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.516: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.517: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.517: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.517: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.517: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.517: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.517: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.518: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.518: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.518: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.518: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.518: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.518: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.519: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.519: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.519: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.519: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.520: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.520: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.520: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.520: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.520: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.520: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.521: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.521: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.521: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.521: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.521: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.521: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.522: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.522: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.522: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.522: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.522: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.522: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.523: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.523: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.523: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.523: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.523: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.523: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.524: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.524: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.524: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.524: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.524: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.524: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.525: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.525: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.525: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.525: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.525: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.525: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.526: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.526: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.526: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.526: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.526: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.526: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.527: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.527: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.527: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.527: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.527: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.527: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.528: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.528: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.528: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.528: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.528: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.528: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.529: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.529: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.529: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.529: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.529: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.529: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.530: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.530: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.530: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.530: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.530: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.530: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.531: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.531: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.531: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.531: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.531: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.531: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.532: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.532: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.532: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.532: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.532: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.532: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.533: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.533: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.534: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.534: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.534: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.534: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.534: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.534: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.535: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.535: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.535: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.535: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.535: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.535: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.536: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.536: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.536: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.536: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.536: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.536: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.537: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.537: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.537: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.537: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.537: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.537: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.538: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.538: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.538: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.538: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.539: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.539: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.539: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.539: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.539: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.539: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.540: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.540: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.540: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.540: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.540: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.540: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.541: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.541: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.541: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.541: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.541: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.541: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.542: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.542: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.542: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.542: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.542: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.542: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.543: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.543: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.543: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.543: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.544: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.544: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.544: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.544: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.545: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.545: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.545: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.545: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.545: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.545: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.546: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.546: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.546: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.546: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.546: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.546: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.547: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.547: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.547: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.547: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.547: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.547: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.548: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.548: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.548: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.548: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.549: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.549: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.549: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.549: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.549: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.549: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.550: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.550: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.550: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.550: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.550: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.550: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.551: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.551: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.551: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.551: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.551: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.551: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.552: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.552: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.552: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.552: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.552: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.552: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.553: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.553: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.553: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.553: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.554: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.554: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.554: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.554: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.555: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.555: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.555: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.555: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.555: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.555: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.556: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.556: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.556: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.556: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.556: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.556: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.557: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.557: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.557: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.557: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.557: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.557: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.558: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.558: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.558: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.558: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.558: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.558: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.559: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.559: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.559: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.559: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.559: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.559: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.560: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.560: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.560: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.560: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.561: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.561: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.561: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.561: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.561: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.561: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.562: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.562: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.562: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.562: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.562: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.562: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.563: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.563: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.563: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.563: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.563: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.563: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.564: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.564: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.564: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.564: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.564: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.564: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.565: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.565: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.565: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.565: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.565: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.565: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.566: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.566: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.566: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.566: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.567: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.567: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.567: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.567: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.568: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.568: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.568: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.568: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.568: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.568: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.569: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.569: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.569: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.569: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.569: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.569: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.570: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.570: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.570: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.570: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.570: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.570: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.571: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.571: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.571: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.571: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.571: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.571: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.572: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.572: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.572: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.572: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.572: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.572: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.573: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.573: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.573: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.573: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.573: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.573: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.574: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.574: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.574: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.574: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.574: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.574: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.575: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.575: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.575: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.575: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.575: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.575: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.576: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.576: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.576: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.576: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.576: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.576: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.577: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.577: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.577: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.577: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.577: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.577: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.578: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.578: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.578: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.578: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.578: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.578: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.579: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.579: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.579: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.579: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.579: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.579: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.580: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.580: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.580: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.580: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.580: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.580: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.581: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.581: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.581: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.581: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.581: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.581: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.582: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.582: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.582: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.582: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.582: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.582: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.583: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.583: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.583: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.583: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.583: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.583: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.584: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.584: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.584: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.584: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.584: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.584: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.584: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.585: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.585: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.585: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.585: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.585: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.586: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.586: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.586: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.587: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.587: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.587: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.587: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.587: variance_after = 1737 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.587: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.587: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.588: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.588: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.588: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.588: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.588: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.588: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.589: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.589: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.589: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.589: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.589: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.589: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.590: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.590: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.590: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.590: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.590: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.590: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.591: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.591: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.591: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.591: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.591: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.591: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.592: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.592: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.593: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.593: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.593: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.593: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.593: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.593: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.594: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.594: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.594: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.594: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.594: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.594: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.595: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.595: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.595: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.595: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.595: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.595: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.596: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.596: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.596: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.596: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.596: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.596: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.597: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.597: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.597: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.597: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.597: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.597: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.598: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.598: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.598: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.598: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.598: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.598: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.599: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.599: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.599: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.599: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.600: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.600: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.600: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.600: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.600: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.600: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.601: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.601: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.601: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.601: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.601: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.601: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.602: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.602: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.602: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.602: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.602: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.602: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.603: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.603: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.603: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.603: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.603: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.603: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.604: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.604: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.604: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.604: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.604: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.604: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.605: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.605: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.605: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.605: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.605: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.605: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.606: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.606: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.606: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.606: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.606: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.606: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.607: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.607: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.607: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.608: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.608: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.608: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.608: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.608: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.609: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.609: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.609: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.609: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.609: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.609: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.610: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.610: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.610: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.610: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.610: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.610: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.611: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.611: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.611: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.611: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.611: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.611: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.612: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.612: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.612: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.612: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.612: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.612: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.613: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.613: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.613: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.613: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.614: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.614: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.614: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.614: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.614: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.614: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.615: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.615: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.615: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.615: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.615: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.615: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.616: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.616: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.616: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.616: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.616: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.616: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.617: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.617: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.617: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.617: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.617: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.617: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.618: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.618: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.618: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.618: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.618: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.618: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.619: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.619: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.619: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.619: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.619: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.619: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.620: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.620: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.620: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.620: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.620: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.620: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.621: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.621: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.621: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.621: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.621: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.622: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.622: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.622: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.623: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.623: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.623: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.623: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.623: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.623: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.624: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.624: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.624: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.624: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.624: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.624: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.625: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.625: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.625: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.625: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.625: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.625: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.626: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.626: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.626: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.626: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.626: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.626: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.627: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.627: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.627: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.627: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.627: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.627: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.628: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.628: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.628: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.628: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.628: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.628: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.629: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.629: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.629: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.629: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.629: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.629: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.630: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.630: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.630: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.630: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.630: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.630: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.631: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.631: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.631: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.631: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.631: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.631: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.632: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.632: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.632: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.632: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.632: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.632: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.633: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.633: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.633: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.633: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.633: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.633: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.634: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.634: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.634: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.634: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.634: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.634: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.635: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.635: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.635: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.635: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.635: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.635: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.636: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.636: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.636: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.636: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.636: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.636: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.637: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.637: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.637: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.637: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.637: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.637: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.638: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.638: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.638: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.638: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.638: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.638: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.639: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.639: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.639: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.639: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.639: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.639: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.640: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.640: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.640: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.640: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.640: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.640: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.641: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.641: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.641: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.641: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.642: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.642: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.642: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.642: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.642: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.642: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.643: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.643: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.643: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.643: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.643: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.643: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.644: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.644: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.644: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.644: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.644: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.644: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.645: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.645: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.645: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.645: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.645: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.645: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.646: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.646: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.647: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.647: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.647: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.647: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.647: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.647: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.648: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.648: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.648: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.648: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.648: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.648: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.649: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.649: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.649: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.649: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.649: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.649: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.650: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.650: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.650: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.650: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.651: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.651: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.651: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.651: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.651: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.651: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.652: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.652: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.652: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.652: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.652: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.652: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.653: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.653: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.653: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.653: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.653: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.653: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.654: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.654: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.654: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.654: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.654: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.654: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.655: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.655: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.656: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.656: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.656: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.656: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.656: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.656: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.657: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.657: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.657: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.657: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.657: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.657: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.658: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.658: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.658: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.658: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.658: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.658: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.659: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.659: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.659: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.659: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.659: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.659: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.660: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.660: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.660: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.660: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.660: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.660: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.661: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.661: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.661: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.661: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.661: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.661: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.662: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.662: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.662: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.662: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.663: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.663: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.663: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.663: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.663: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.663: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.664: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.664: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.664: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.664: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.664: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.664: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.665: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.665: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.665: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.665: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.666: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.666: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.666: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.666: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.667: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.667: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.667: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.667: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.667: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.667: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.668: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.668: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.668: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.668: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.668: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.668: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.669: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.669: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.669: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.669: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.669: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.669: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.670: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.670: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.670: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.670: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.670: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.670: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.671: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.671: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.671: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.671: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.671: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.671: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.672: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.672: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.672: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.672: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.672: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.672: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.673: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.673: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.673: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.673: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.673: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.674: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.674: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.674: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.674: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.674: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.674: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.675: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.675: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.675: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.675: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.675: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.676: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.676: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.676: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.676: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.676: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.676: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.677: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.677: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.677: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.677: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.677: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.677: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.678: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.678: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.678: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.678: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.678: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.678: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.679: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.679: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.679: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.679: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.679: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.679: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.680: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.680: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.680: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.680: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.680: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.680: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.681: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.681: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.681: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.681: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.681: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.681: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.682: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.682: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.682: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.682: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.682: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.682: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.683: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.683: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.683: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.683: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.683: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.683: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.684: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.684: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.684: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.684: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.684: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.684: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.685: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.685: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.685: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.685: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.685: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.685: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.686: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.686: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.686: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.687: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.687: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.687: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.687: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.687: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.688: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.688: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.688: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.688: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.688: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.688: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.689: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.689: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.689: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.689: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.689: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.689: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.690: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.690: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.690: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.690: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.690: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.690: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.691: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.691: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.691: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.691: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.691: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.691: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.692: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.692: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.692: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.692: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.692: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.692: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.693: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.693: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.693: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.693: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.693: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.693: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.694: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.694: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.694: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.694: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.694: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.694: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.695: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.695: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.695: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.695: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.695: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.695: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.696: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.696: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.696: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.696: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.696: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.696: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.697: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.697: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.697: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.697: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.697: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.697: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.698: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.698: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.698: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.698: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.698: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.698: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.699: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.699: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.699: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.699: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.699: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.699: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.700: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.700: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.700: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.700: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.700: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.700: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.701: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.701: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.701: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.701: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.702: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.702: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.702: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.702: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.702: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.702: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.703: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.703: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.703: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.703: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.703: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.703: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.704: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.704: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.704: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.704: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.704: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.704: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.705: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.705: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.706: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.706: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.706: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.706: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.706: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.706: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.707: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.707: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.707: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.707: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.707: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.707: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.708: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.708: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.708: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.708: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.708: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.708: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.709: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.709: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.709: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.709: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.710: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.710: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.710: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.710: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.710: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.710: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.711: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.711: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.711: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.711: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.711: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.711: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.712: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.712: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.713: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.713: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.713: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.713: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.713: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.713: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.714: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.714: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.714: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.714: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.714: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.714: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.715: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.715: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.715: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.715: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.715: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.715: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.716: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.716: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.716: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.716: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.716: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.717: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.717: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.717: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.717: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.717: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.718: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.718: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.718: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.718: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.718: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.718: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.719: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.719: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.719: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.719: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.719: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.719: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.720: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.720: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.721: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.721: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.721: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.721: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.721: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.721: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.722: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.722: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.722: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.722: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.722: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.722: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.723: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.723: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.723: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.723: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.724: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.724: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.724: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.724: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.724: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.724: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.725: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.725: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.725: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.725: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.726: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.726: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.726: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.726: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.727: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.727: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.727: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.727: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.727: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.727: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.728: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.728: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.728: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.728: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.728: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.729: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.729: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.729: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.729: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.729: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.730: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.730: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.730: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.730: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.730: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.730: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.731: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.731: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.731: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.731: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.731: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.731: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.732: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.732: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.732: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.732: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.732: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.732: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.733: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.733: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.733: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.733: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.733: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.733: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.734: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.734: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.734: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.735: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.735: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.735: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.735: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.735: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.736: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.736: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.736: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.736: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.736: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.736: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.737: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.737: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.737: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.737: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.737: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.737: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.738: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.738: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.738: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.738: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.738: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.738: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.739: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.739: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.739: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.739: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.739: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.739: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.740: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.740: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.740: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.740: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.741: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.741: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.741: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.741: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.741: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.741: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.741: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.742: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.742: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.742: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.742: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.742: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.743: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.743: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.743: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.743: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.743: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.744: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.744: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.744: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.744: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.744: variance_after = 1526 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.744: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.744: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.745: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.745: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.746: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.746: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.746: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.746: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.746: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.746: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.747: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.747: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.747: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.747: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.747: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.747: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.748: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.748: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.748: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.748: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.748: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.748: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.749: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.749: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.749: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.749: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.749: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.749: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.750: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.750: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.750: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.750: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.750: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.750: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.751: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.751: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.751: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.751: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.751: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.751: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.752: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.752: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.752: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.752: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.753: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.753: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.753: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.753: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.753: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.753: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.754: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.754: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.754: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.754: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.754: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.754: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.755: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.755: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.755: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.755: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.755: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.755: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.756: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.756: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.756: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.756: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.756: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.756: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.757: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.757: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.757: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.757: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.757: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.757: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.758: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.758: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.758: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.758: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.758: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.758: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.759: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.759: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.760: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.760: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.760: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.760: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.760: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.760: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.761: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.761: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.761: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.761: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.761: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.761: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.762: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.762: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.762: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.762: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.762: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.762: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.763: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.763: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.763: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.763: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.763: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.763: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.764: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.764: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.764: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.764: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.764: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.764: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.765: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.765: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.765: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.765: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.765: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.765: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.766: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.766: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.766: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.766: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.766: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.766: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.767: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.767: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.767: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.767: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.768: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.768: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.768: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.768: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.768: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.768: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.769: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.769: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.769: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.769: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.769: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.769: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.770: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.770: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.770: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.770: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.770: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.770: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.771: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.771: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.771: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.771: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.771: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.771: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.772: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.772: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.772: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.772: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.772: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.772: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.773: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.773: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.774: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.774: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.774: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.774: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.774: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.774: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.775: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.775: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.775: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.775: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.775: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.775: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.776: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.776: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.776: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.776: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.776: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.776: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.777: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.777: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.777: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.777: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.777: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.777: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.778: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.778: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.778: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.778: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.778: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.778: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.779: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.779: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.779: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.779: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.780: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.780: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.780: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.780: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.780: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.780: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.781: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.781: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.781: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.781: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.781: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.781: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.782: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.782: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.782: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.782: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.782: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.782: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.783: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.783: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.783: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.783: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.783: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.783: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.784: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.784: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.785: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.785: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.785: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.785: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.785: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.785: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.786: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.786: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.786: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.786: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.786: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.786: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.787: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.787: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.787: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.787: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.787: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.787: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.788: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.788: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.788: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.788: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.788: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.788: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.789: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.789: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.789: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.789: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.789: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.789: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.790: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.790: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.790: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.790: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.790: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.790: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.791: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.791: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.791: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.791: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.791: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.791: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.792: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.792: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.792: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.792: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.792: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.792: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.793: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.793: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.793: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.793: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.793: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.793: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.794: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.794: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.794: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.794: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.794: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.794: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.795: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.795: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.795: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.795: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.795: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.795: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.796: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.796: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.796: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.796: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.797: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.797: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.797: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.797: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.797: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.797: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.798: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.798: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.798: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.798: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.798: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.798: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.799: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.799: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.799: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.799: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.799: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.799: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.800: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.800: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.800: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.800: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.800: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.800: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.801: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.801: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.801: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.801: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.801: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.801: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.802: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.802: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.802: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.802: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.802: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.802: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.803: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.803: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.803: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.803: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.803: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.803: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.804: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.804: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.805: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.805: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.805: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.805: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.805: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.805: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.806: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.806: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.806: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.806: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.806: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.806: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.807: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.807: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.807: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.807: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.807: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.807: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.808: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.808: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.808: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.808: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.808: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.808: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.809: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.809: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.809: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.809: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.809: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.809: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.810: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.810: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.810: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.810: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.810: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.810: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.811: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.811: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.811: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.811: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.811: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.811: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.812: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.812: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.812: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.812: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.812: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.812: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.813: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.813: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.813: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.813: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.813: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.813: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.814: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.814: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.814: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.814: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.814: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.814: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.815: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.815: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.815: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.815: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.815: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.815: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.816: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.816: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.816: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.816: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.817: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.817: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.817: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.817: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.817: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.817: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.818: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.818: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.818: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.818: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.818: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.818: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.819: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.819: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.819: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.819: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.819: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.819: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.820: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.820: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.820: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.820: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.820: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.820: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.821: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.821: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.821: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.821: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.821: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.821: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.822: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.822: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.822: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.822: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.822: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.822: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.823: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.823: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.824: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.824: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.824: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.824: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.824: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.824: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.825: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.825: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.825: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.825: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.825: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.825: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.826: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.826: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.826: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.826: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.826: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.826: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.827: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.827: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.827: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.827: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.827: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.827: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.828: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.828: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.828: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.828: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.828: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.828: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.829: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.829: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.829: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.829: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.829: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.829: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.830: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.830: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.830: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.830: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.831: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.831: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.831: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.831: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.831: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.831: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.832: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.832: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.832: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.832: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.832: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.832: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.833: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.833: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.833: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.833: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.833: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.833: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.834: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.834: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.834: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.834: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.834: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.834: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.835: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.835: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.835: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.835: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.835: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.835: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.836: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.836: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.836: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.836: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.836: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.836: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.837: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.837: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.838: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.838: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.838: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.838: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.838: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.838: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.839: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.839: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.839: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.839: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.839: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.839: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.840: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.840: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.840: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.840: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.840: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.840: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.841: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.841: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.841: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.841: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.841: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.841: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.842: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.842: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.842: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.842: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.842: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.842: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.843: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.843: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.843: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.843: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.843: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.843: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.844: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.844: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.844: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.844: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.844: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.844: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.845: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.845: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.845: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.845: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.845: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.846: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.846: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.846: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.846: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.846: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.847: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.847: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.847: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.847: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.847: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.847: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.848: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.848: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.848: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.848: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.848: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.848: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.849: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.849: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.849: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.849: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.849: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.849: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.850: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.850: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.850: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.850: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.850: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.850: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.851: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.851: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.851: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.851: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.851: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.851: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.852: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.852: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.852: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.852: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.852: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.852: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.853: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.853: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.853: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.853: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.853: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.853: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.854: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.854: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.854: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.854: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.854: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.854: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.855: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.855: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.855: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.855: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.855: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.855: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.856: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.856: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.856: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.856: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.856: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.856: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.857: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.857: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.857: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.857: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.857: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.857: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.858: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.858: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.859: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.859: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.859: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.859: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.859: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.859: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.860: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.860: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.860: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.860: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.860: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.860: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.861: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.861: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.861: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.861: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.861: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.861: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.862: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.862: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.862: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.862: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.862: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.862: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.863: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.863: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.863: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.863: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.863: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.863: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.864: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.864: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.864: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.864: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.865: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.865: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.865: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.865: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.865: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.865: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.866: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.866: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.866: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.866: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.866: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.866: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.867: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.867: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.867: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.867: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.867: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.867: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.868: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.868: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.869: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.869: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.869: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.869: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.870: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.870: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.871: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.871: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.871: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.871: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.871: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.871: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.872: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.872: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.872: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.872: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.873: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.873: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.874: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.874: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.874: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.874: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.874: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.874: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.875: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.875: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.875: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.875: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.875: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.875: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.876: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.876: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.876: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.876: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.876: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.876: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.877: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.877: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.877: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.877: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.878: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.878: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.878: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.878: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.878: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.878: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.879: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.879: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.879: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.879: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.879: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.879: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.880: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.880: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.880: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.880: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.880: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.880: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.881: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.881: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.881: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.881: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.881: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.881: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.882: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.882: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.882: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.882: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.882: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.882: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.883: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.883: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.883: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.883: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.884: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.884: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.884: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.884: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.885: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.885: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.885: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.885: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.885: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.885: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.886: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.886: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.886: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.886: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.886: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.886: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.887: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.887: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.887: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.887: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.887: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.887: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.888: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.888: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.888: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.888: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.888: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.888: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.889: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.889: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.889: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.889: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.889: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.889: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.890: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.890: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.890: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.890: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.890: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.890: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.891: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.891: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.891: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.891: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.891: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.891: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.892: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.892: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.892: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.892: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.892: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.892: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.893: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.893: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.893: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.893: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.893: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.893: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.894: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.894: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.894: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.894: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.894: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.894: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.895: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.895: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.895: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.895: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.895: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.895: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.896: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.896: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.896: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.896: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.896: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.896: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.897: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.897: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.897: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.897: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.898: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.898: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.898: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.898: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.898: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.898: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.899: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.899: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.899: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.899: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.899: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.899: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.900: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.900: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.900: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.900: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.900: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.900: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.901: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.901: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.901: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.901: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.901: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.901: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.902: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.902: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.902: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.902: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.902: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.902: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.903: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.903: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.903: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.903: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.903: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.903: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.903: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.904: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.904: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.904: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.904: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.904: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.905: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.905: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.905: [vfs7552] CAPTURE_NUM_STATES entering state 2 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.905: [vfs7552] REQUEST CHUNK entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.905: Sending vfs7552_read_image_chunk 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.906: [vfs7552] REQUEST CHUNK completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.906: [vfs7552] CAPTURE_NUM_STATES entering state 3 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.906: [vfs7552] CAPTURE_NUM_STATES entering state 4 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.906: Cleaning image 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.906: variance_after = 1435 431s 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.906: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.906: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.907: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.907: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.907: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.907: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.907: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.907: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.908: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.908: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.908: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.908: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.908: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.908: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.909: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.909: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.909: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.909: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.909: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.909: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.910: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.910: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.911: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.911: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.911: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.911: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.911: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.911: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.912: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.912: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.912: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.912: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.912: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.912: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.913: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.913: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.913: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.913: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.913: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.913: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.914: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.914: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.914: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.914: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.914: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.914: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.915: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.915: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.915: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.915: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.915: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.915: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.916: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.916: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.916: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.916: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.916: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.916: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.917: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.917: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.917: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.917: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.917: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.917: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.918: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.918: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.918: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.918: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.919: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.919: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.919: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.919: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.919: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.919: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.920: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.920: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.920: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.920: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.920: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.920: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.921: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.921: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.921: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.921: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.921: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.921: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.922: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.922: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.922: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.922: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.922: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.922: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.923: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.923: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.923: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.923: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.923: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.923: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.924: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.924: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.924: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.924: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.924: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.924: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.925: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.925: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.925: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.925: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.925: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.925: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.926: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.926: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.927: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.927: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.927: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.927: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.927: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.927: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.928: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.928: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.928: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.928: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.928: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.928: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.929: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.929: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.929: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.929: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.929: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.929: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.930: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.930: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.930: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.930: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.930: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.930: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.931: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.931: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.931: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.931: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.931: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.931: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.932: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.932: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.932: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.932: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.932: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.932: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.933: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.933: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.933: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.933: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.933: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.933: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.934: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.934: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.934: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.934: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.935: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.935: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.935: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.935: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.935: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.935: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.936: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.936: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.936: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.936: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.936: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.936: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.937: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.937: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.937: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.937: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.937: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.937: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.938: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.938: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.938: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.938: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.938: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.938: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.939: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.939: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.939: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.939: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.939: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.939: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.940: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.940: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.940: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.940: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.940: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.940: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.941: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.941: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.941: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.941: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.941: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.941: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.942: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.942: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.942: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.942: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.942: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.942: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.943: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.943: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.944: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.944: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.944: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.944: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.944: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.944: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.945: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.945: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.945: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.945: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.945: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.945: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.946: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.946: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.946: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.946: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.946: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.946: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.947: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.947: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.947: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.947: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.947: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.947: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.948: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.948: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.948: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.948: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.948: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.948: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.949: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.949: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.949: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.949: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.949: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.949: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.950: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.950: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.950: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.950: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.950: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.950: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.951: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.951: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.951: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.951: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.951: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.951: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.952: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.952: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.952: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.952: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.952: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.952: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.953: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.953: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.953: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.953: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.953: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.953: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.954: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.954: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.954: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.954: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.955: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.955: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.955: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.955: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.955: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.955: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.956: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.956: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.956: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.956: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.956: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.956: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.957: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.957: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.957: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.957: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.957: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.957: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.958: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.958: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.958: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.958: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.958: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.958: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.959: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.959: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.959: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.959: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.959: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.959: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.960: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.960: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.960: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.960: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.960: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.960: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.961: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.961: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.961: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.961: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.961: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.961: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.962: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.962: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.962: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.962: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.962: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.962: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.963: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.963: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.963: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.963: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.963: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.963: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.964: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.964: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.964: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.964: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.964: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.964: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.965: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.965: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.965: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.965: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.965: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.965: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.966: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.966: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.966: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.966: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.966: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.966: Sending vfs7552_is_image_ready 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.967: [vfs7552] QUERY DATA READY entering state 1 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.967: Receiving 64 bytes 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.967: Got 6 bytes out of 64 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.967: [vfs7552] QUERY DATA READY completed successfully 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 431s (process:2196): libfprint-SSM-DEBUG: 05:09:11.967: [vfs7552] QUERY DATA READY entering state 0 431s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.967: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.968: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.968: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.968: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.968: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.968: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.968: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.969: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.969: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.969: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.969: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.969: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.969: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.970: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.970: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.970: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.970: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.970: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.970: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.971: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.971: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.971: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.971: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.971: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.971: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.972: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.972: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.972: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.972: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.972: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.972: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.973: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.973: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.973: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.973: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.973: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.973: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.974: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.974: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.974: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.974: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.974: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.974: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.975: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.975: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.975: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.975: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.975: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.975: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.976: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.976: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.976: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.976: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.976: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.976: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.977: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.977: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.977: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.977: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.977: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.977: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.978: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.978: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.978: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.978: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.978: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.978: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.979: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.979: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.979: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.979: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.979: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.979: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.980: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.980: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.980: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.980: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.980: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.980: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.981: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.981: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.981: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.982: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.982: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.982: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.982: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.982: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.983: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.983: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.983: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.983: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.983: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.983: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.984: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.984: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.984: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.984: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.984: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.984: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.985: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.985: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.985: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.985: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.985: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.985: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.986: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.986: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.986: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.986: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.986: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.986: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.987: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.987: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.987: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.987: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.987: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.987: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.988: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.988: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.988: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.988: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.988: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.988: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.989: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.989: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.989: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.989: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.989: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.989: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.990: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.990: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.990: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.990: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.990: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.990: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.991: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.991: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.991: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.991: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.991: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.991: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.992: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.992: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.992: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.992: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.992: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.992: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.993: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.993: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.993: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.993: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.993: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.993: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.994: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.994: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.994: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.994: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.994: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.994: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.995: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.995: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.995: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.995: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.995: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.995: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.996: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.996: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.996: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.996: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.996: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.997: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.997: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.997: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.997: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.997: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.997: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.997: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.998: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.998: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.998: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.998: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.999: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.999: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.999: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.999: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:11.999: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:11.999: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.000: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.000: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.000: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.000: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.000: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.000: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.001: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.001: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.001: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.001: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.001: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.001: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.002: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.002: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.002: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.002: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.002: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.002: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.003: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.003: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.003: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.003: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.003: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.003: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.004: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.004: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.004: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.004: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.004: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.004: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.005: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.005: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.005: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.005: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.005: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.005: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.006: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.006: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.007: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.007: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.007: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.007: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.007: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.007: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.008: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.008: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.008: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.008: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.008: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.008: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.009: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.009: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.009: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.009: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.009: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.009: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.010: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.010: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.010: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.010: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.010: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.010: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.011: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.011: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.011: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.011: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.011: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.011: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.012: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.012: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.012: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.012: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.012: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.012: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.013: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.013: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.013: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.013: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.013: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.013: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.014: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.014: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.014: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.014: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.014: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.014: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.015: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.015: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.015: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.015: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.016: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.016: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.016: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.016: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.016: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.016: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.017: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.017: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.017: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.017: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.017: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.017: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.018: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.018: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.018: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.018: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.018: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.018: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.019: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.019: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.019: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.019: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.019: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.019: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.020: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.020: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.021: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.021: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.021: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.021: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.021: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.021: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.022: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.022: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.022: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.022: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.022: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.022: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.023: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.023: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.023: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.023: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.023: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.023: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.024: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.024: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.024: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.024: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.024: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.024: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.025: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.025: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.025: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.025: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.025: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.025: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.026: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.026: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.026: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.026: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.026: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.026: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.027: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.027: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.027: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.027: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.027: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.027: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.028: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.028: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.028: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.028: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.029: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.029: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.029: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.029: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.029: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.029: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.030: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.030: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.030: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.030: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.030: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.030: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.031: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.031: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.031: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.031: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.031: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.031: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.032: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.032: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.032: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.032: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.032: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.032: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.033: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.033: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.033: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.033: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.033: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.033: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.034: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.034: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.034: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.034: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.034: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.034: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.035: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.035: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.035: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.035: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.035: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.035: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.036: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.036: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.036: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.036: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.036: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.036: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.037: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.037: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.037: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.037: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.037: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.037: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.038: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.038: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.038: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.038: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.038: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.038: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.039: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.039: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.039: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.039: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.039: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.039: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.040: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.040: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.041: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.041: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.041: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.041: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.041: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.041: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.042: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.042: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.042: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.042: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.042: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.042: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.043: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.043: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.043: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.043: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.043: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.043: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.044: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.044: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.044: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.044: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.044: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.044: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.045: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.045: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.045: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.045: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.045: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.045: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.046: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.046: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.046: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.046: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.046: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.046: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.047: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.047: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.047: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.047: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.047: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.047: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.048: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.048: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.048: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.048: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.048: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.048: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.049: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.049: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.049: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.049: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.049: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.049: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.050: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.050: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.050: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.050: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.050: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.050: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.051: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.051: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.051: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.051: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.051: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.051: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.052: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.052: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.052: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.052: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.052: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.052: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.053: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.053: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.053: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.053: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.053: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.053: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.054: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.054: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.054: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.054: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.054: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.054: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.055: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.055: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.055: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.055: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.055: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.055: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.056: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.056: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.056: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.056: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.057: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.057: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.057: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.057: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.057: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.057: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.057: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.057: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.058: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.058: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.058: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.058: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.059: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.059: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.059: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.059: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.059: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.060: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.060: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.060: [vfs7552] CAPTURE_NUM_STATES entering state 4 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.060: Cleaning image 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.060: variance_after = 1425 432s 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.060: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.060: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.061: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.061: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.061: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.061: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.061: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.061: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.062: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.062: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.062: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.062: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.062: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.062: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.063: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.063: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.063: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.063: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.063: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.063: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.064: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.064: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.064: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.064: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.064: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.064: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.065: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.065: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.065: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.065: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.065: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.065: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.066: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.066: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.066: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.066: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.066: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.066: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.067: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.067: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.067: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.068: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.068: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.068: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.068: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.068: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.069: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.069: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.069: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.069: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.069: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.069: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.070: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.070: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.070: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.070: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.070: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.070: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.071: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.071: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.071: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.071: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.071: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.071: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.072: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.072: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.072: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.072: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.072: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.072: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.073: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.073: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.073: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.073: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.073: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.073: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.074: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.074: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.074: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.074: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.074: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.074: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.075: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.075: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.075: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.075: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.076: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.076: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.076: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.076: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.076: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.076: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.077: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.077: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.077: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.077: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.077: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.077: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.078: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.078: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.078: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.078: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.078: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.078: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.079: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.079: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.079: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.079: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.079: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.079: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.080: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.080: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.080: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.080: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.080: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.080: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.081: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.081: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.081: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.081: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.081: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.081: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.082: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.082: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.082: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.082: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.082: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.082: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.083: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.083: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.083: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.083: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.083: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.083: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.084: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.084: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.084: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.084: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.084: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.084: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.085: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.085: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.085: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.085: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.085: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.085: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.086: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.086: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.086: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.086: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.086: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.086: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.087: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.087: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.087: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.087: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.087: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.087: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.088: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.088: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.088: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.088: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.088: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.088: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.089: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.089: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.090: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.090: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.090: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.090: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.090: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.090: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.091: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.091: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.091: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.091: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.091: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.091: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.092: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.092: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.092: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.092: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.092: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.092: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.093: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.093: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.093: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.093: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.093: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.093: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.094: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.094: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.094: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.094: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.094: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.094: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.095: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.095: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.095: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.095: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.095: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.095: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.096: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.096: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.096: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.096: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.096: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.096: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.097: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.097: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.097: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.097: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.097: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.097: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.098: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.098: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.098: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.098: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.098: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.098: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.099: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.099: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.099: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.099: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.100: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.100: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.100: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.100: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.100: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.100: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.101: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.101: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.101: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.101: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.101: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.101: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.102: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.102: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.102: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.102: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.102: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.102: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.103: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.103: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.103: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.103: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.103: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.103: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.104: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.104: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.104: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.104: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.104: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.104: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.105: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.105: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.105: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.105: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.105: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.105: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.106: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.106: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.106: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.106: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.106: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.106: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.107: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.107: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.107: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.107: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.107: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.107: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.108: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.108: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.108: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.108: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.108: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.108: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.109: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.109: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.109: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.109: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.109: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.109: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.110: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.110: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.110: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.110: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.110: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.110: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.111: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.111: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.111: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.111: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.112: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.112: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.112: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.112: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.112: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.113: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.113: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.113: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.113: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.113: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.113: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.113: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.113: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.113: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.114: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.114: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.114: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.114: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.114: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.114: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.115: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.115: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.115: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.115: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.115: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.115: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.116: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.116: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.117: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.117: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.117: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.117: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.117: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.117: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.118: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.118: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.118: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.118: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.118: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.118: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.119: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.119: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.119: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.119: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.119: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.119: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.120: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.120: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.120: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.120: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.120: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.120: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.121: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.121: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.121: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.121: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.121: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.121: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.122: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.122: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.122: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.122: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.122: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.122: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.123: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.123: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.123: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.123: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.123: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.123: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.124: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.124: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.124: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.124: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.124: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.124: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.125: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.125: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.125: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.125: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.125: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.125: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.126: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.126: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.126: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.126: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.126: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.126: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.127: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.127: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.127: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.127: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.127: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.127: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.128: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.128: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.128: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.128: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.128: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.128: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.128: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.129: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.129: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.129: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.129: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.129: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.130: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.130: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.130: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.130: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.130: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.131: [vfs7552] CAPTURE_NUM_STATES entering state 4 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.131: Cleaning image 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.131: variance_after = 1532 432s 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.131: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.131: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.131: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.131: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.132: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.132: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.132: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.132: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.132: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.132: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.133: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.133: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.133: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.133: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.133: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.133: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.134: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.134: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.134: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.134: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.135: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.135: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.135: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.135: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.135: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.135: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.136: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.136: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.136: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.136: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.136: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.136: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.137: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.137: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.137: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.137: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.137: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.137: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.138: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.138: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.138: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.138: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.138: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.138: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.139: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.139: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.139: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.139: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.139: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.139: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.140: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.140: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.140: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.140: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.140: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.140: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.141: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.141: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.141: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.141: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.141: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.141: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.142: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.142: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.142: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.142: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.142: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.142: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.143: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.143: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.143: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.143: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.143: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.143: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.144: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.144: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.144: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.144: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.144: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.144: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.145: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.145: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.145: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.145: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.145: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.145: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.146: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.146: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.146: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.146: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.146: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.146: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.147: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.147: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.147: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.147: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.147: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.147: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.148: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.148: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.148: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.148: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.148: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.148: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.149: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.149: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.149: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.149: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.149: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.149: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.150: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.150: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.150: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.150: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.150: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.150: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.151: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.151: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.151: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.151: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.151: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.151: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.152: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.152: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.152: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.152: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.152: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.152: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.153: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.153: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.153: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.153: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.153: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.153: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.154: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.154: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.154: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.154: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.154: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.154: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.155: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.155: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.156: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.156: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.156: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.156: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.156: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.156: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.157: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.157: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.157: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.157: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.157: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.157: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.158: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.158: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.158: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.158: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.158: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.158: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.159: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.159: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.159: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.159: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.159: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.159: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.160: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.160: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.160: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.160: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.160: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.160: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.161: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.161: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.161: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.161: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.161: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.161: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.162: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.162: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.162: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.162: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.162: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.162: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.163: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.163: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.163: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.163: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.163: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.163: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.164: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.164: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.164: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.164: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.164: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.164: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.165: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.165: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.165: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.165: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.165: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.165: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.166: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.166: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.166: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.166: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.166: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.166: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.167: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.167: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.167: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.167: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.168: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.168: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.168: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.168: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.168: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.168: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.169: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.169: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.169: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.169: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.169: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.169: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.170: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.170: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.170: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.170: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.170: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.170: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.170: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.171: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.171: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.171: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.171: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.171: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.172: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.172: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.172: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.172: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.172: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.173: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.173: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.173: [vfs7552] CAPTURE_NUM_STATES entering state 4 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.173: Cleaning image 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.173: variance_after = 1691 432s 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.173: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.173: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.174: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.174: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.174: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.174: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.174: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.174: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.175: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.175: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.175: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.175: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.175: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.175: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.176: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.176: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.176: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.176: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.176: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.176: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.177: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.177: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.177: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.177: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.177: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.177: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.178: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.178: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.178: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.178: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.178: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.178: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.179: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.179: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.179: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.180: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.180: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.180: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.180: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.180: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.181: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.181: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.181: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.181: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.181: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.181: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.182: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.182: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.182: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.182: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.182: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.182: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.183: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.183: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.183: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.183: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.183: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.183: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.184: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.184: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.184: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.184: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.184: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.184: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.185: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.185: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.185: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.185: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.186: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.186: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.186: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.186: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.186: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.186: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.187: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.187: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.187: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.187: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.187: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.187: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.188: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.188: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.188: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.188: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.188: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.188: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.189: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.189: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.189: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.189: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.189: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.189: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.190: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.190: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.190: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.190: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.191: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.191: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.191: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.191: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.192: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.192: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.192: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.192: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.192: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.192: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.193: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.193: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.193: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.193: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.193: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.193: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.194: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.194: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.194: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.194: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.194: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.194: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.195: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.195: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.195: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.195: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.195: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.195: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.196: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.196: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.196: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.196: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.197: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.197: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.197: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.197: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.197: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.197: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.198: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.198: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.198: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.198: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.198: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.198: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.199: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.199: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.199: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.199: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.199: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.199: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.200: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.200: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.201: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.201: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.201: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.201: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.201: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.201: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.202: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.202: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.202: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.202: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.202: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.202: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.203: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.203: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.203: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.203: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.203: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.203: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.204: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.204: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.204: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.204: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.204: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.204: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.205: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.205: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.205: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.205: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.206: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.206: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.206: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.206: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.206: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.206: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.207: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.207: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.207: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.207: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.207: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.207: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.208: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.208: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.208: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.208: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.208: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.208: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.209: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.209: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.210: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.210: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.210: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.210: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.210: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.210: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.211: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.211: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.211: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.211: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.211: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.211: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.212: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.212: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.212: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.212: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.212: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.212: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.213: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.213: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.213: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.213: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.213: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.213: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.214: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.214: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.214: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.214: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.214: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.214: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.215: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.215: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.215: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.215: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.216: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.216: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.216: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.216: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.216: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.216: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.217: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.217: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.217: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.217: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.217: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.217: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.217: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.218: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.218: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.218: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.218: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.218: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.219: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.219: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.219: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.220: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.220: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.220: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.220: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.221: [vfs7552] CAPTURE_NUM_STATES entering state 4 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.221: Cleaning image 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.221: variance_after = 1845 432s 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.221: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.221: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.221: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.221: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.222: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.222: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.222: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.222: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.222: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.222: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.223: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.223: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.223: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.223: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.223: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.223: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.224: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.224: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.224: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.224: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.224: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.224: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.225: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.225: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.225: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.225: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.225: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.226: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.226: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.226: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.226: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.226: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.227: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.227: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.227: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.227: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.227: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.227: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.228: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.228: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.228: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.228: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.228: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.228: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.229: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.229: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.229: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.229: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.229: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.229: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.230: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.230: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.230: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.230: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.231: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.231: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.231: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.231: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.232: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.232: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.232: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.232: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.232: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.232: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.233: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.233: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.233: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.233: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.233: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.233: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.234: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.234: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.234: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.234: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.234: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.234: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.235: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.235: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.235: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.235: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.236: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.236: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.236: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.236: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.236: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.236: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.237: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.237: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.237: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.237: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.237: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.237: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.238: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.238: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.239: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.239: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.239: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.239: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.239: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.239: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.240: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.240: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.240: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.240: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.241: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.241: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.241: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.241: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.241: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.241: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.242: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.242: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.243: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.243: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.243: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.243: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.243: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.243: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.244: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.244: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.244: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.244: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.245: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.245: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.245: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.245: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.245: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.245: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.246: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.246: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.247: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.247: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.247: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.247: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.248: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.248: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.248: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.248: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.248: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.248: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.249: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.249: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.250: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.250: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.250: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.250: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.251: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.251: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.252: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.252: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.252: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.252: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.252: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.252: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.253: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.253: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.253: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.253: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.254: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.254: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.255: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.255: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.255: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.255: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.256: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.256: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.256: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.256: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.256: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.256: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.257: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.257: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.258: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.258: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.258: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.258: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.258: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.258: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.259: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.259: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.259: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.259: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.260: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.260: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.260: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.260: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.260: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.260: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.261: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.261: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.261: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.261: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.261: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.261: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.262: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.262: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.262: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.262: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.263: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.263: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.263: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.263: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.264: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.264: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.264: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.264: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.264: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.264: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.265: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.265: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.265: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.265: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.265: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.265: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.266: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.266: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.266: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.266: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.266: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.267: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.267: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.267: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.267: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.267: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.268: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.268: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.268: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.268: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.268: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.268: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.269: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.269: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.269: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.269: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.269: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.269: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.270: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.270: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.270: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.270: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.270: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.270: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.271: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.271: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.271: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.271: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.271: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.271: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.272: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.272: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.272: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.272: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.273: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.273: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.273: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.273: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.274: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.274: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.274: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.274: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.274: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.274: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.275: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.275: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.275: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.275: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.275: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.275: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.276: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.276: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.276: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.276: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.276: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.276: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.276: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.277: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.277: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.277: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.277: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.277: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.278: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.278: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.278: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.278: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.278: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.279: [vfs7552] CAPTURE_NUM_STATES entering state 4 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.279: Cleaning image 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.279: variance_after = 2342 432s 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.279: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.279: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.279: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.279: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.280: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.280: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.280: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.280: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.281: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.281: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.281: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.281: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.281: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.281: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.282: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.282: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.282: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.282: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.282: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.282: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.283: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.283: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.283: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.283: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.283: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.283: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.284: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.284: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.284: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.284: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.284: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.284: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.285: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.285: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.285: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.285: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.285: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.285: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.286: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.286: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.286: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.287: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.287: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.287: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.287: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.287: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.288: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.288: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.288: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.288: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.288: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.288: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.289: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.289: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.289: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.289: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.289: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.289: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.290: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.290: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.290: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.290: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.290: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.290: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.291: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.291: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.291: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.291: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.291: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.291: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.292: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.292: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.292: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.292: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.292: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.292: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.293: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.293: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.293: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.293: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.294: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.294: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.294: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.294: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.294: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.294: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.295: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.295: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.295: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.295: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.295: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.295: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.296: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.296: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.296: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.296: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.296: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.296: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.297: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.297: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.297: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.297: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.297: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.297: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.298: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.298: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.298: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.298: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.298: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.298: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.299: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.299: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.299: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.299: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.299: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.299: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.300: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.300: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.301: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.301: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.301: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.301: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.301: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.301: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.302: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.302: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.302: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.302: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.302: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.302: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.303: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.303: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.303: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.303: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.303: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.303: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.304: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.304: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.304: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.304: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.304: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.304: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.305: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.305: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.305: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.305: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.306: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.306: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.306: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.306: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.306: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.306: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.307: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.307: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.307: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.307: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.307: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.307: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.308: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.308: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.308: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.308: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.308: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.308: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.309: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.309: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.309: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.309: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.309: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.309: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.310: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.310: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.310: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.310: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.310: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.310: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.311: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.311: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.311: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.311: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.311: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.311: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.312: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.312: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.312: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.312: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.312: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.312: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.313: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.313: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.313: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.313: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.313: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.314: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.314: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.314: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.315: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.315: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.315: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.315: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.315: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.315: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.316: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.316: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.316: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.316: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.316: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.316: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.317: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.317: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.317: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.317: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.317: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.317: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.318: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.318: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.318: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.318: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.319: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.319: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.319: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.319: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.319: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.319: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.320: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.320: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.321: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.321: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.321: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.321: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.321: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.321: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.322: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.322: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.322: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.322: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.322: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.322: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.323: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.323: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.323: [vfs7552] QUERY DATA READY entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.323: Sending vfs7552_is_image_ready 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.323: [vfs7552] QUERY DATA READY entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.324: Receiving 64 bytes 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.324: Got 6 bytes out of 64 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.324: [vfs7552] QUERY DATA READY completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.324: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.324: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.324: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.325: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.325: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.326: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.326: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.326: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.327: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.327: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.327: [vfs7552] CAPTURE_NUM_STATES entering state 2 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.328: [vfs7552] REQUEST CHUNK entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.328: Sending vfs7552_read_image_chunk 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.328: [vfs7552] REQUEST CHUNK completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.328: [vfs7552] CAPTURE_NUM_STATES entering state 3 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.329: [vfs7552] CAPTURE_NUM_STATES entering state 4 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.329: Cleaning image 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.329: variance_after = 16 432s 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.329: [vfs7552] CAPTURE_NUM_STATES completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.329: [vfs7552] DEACTIVATE_NUM_STATES entering state 0 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.339: [vfs7552] DEACTIVATE_NUM_STATES entering state 1 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.339: [vfs7552] STOP CAPTURE entering state 0 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.339: Sending vfs7552_cmd_04 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.340: [vfs7552] STOP CAPTURE entering state 1 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.340: Receiving 64 bytes 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.341: [vfs7552] STOP CAPTURE entering state 2 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.341: Sending vfs7552_cmd_52 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.341: [vfs7552] STOP CAPTURE entering state 3 432s (process:2196): libfprint-vfs7552-DEBUG: 05:09:12.341: Receiving 64 bytes 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.342: [vfs7552] STOP CAPTURE completed successfully 432s (process:2196): libfprint-SSM-DEBUG: 05:09:12.342: [vfs7552] DEACTIVATE_NUM_STATES completed successfully 432s (process:2196): libfprint-device-DEBUG: 05:09:12.342: Device reported finger status change: FP_FINGER_STATUS_NONE 432s (process:2196): libfprint-image_device-DEBUG: 05:09:12.342: Image device reported finger status: off 432s (process:2196): libfprint-image_device-DEBUG: 05:09:12.342: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 432s (process:2196): libfprint-image_device-DEBUG: 05:09:12.342: Deactivating image device 432s (process:2196): libfprint-image_device-DEBUG: 05:09:12.342: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 432s (process:2196): libfprint-image_device-DEBUG: 05:09:12.342: Image device deactivation completed 432s (process:2196): libfprint-image_device-DEBUG: 05:09:12.342: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 432s (process:2196): libfprint-device-DEBUG: 05:09:12.342: Device reported capture completion 432s (process:2196): libfprint-device-DEBUG: 05:09:12.342: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 432s (process:2196): libfprint-device-DEBUG: 05:09:12.342: Updated temperature model after 2.68 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 432s (process:2196): libfprint-image_device-DEBUG: 05:09:12.342: Image device close completed 432s (process:2196): libfprint-device-DEBUG: 05:09:12.342: Device reported close completion 432s (process:2196): libfprint-device-DEBUG: 05:09:12.343: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 432s (process:2196): libfprint-device-DEBUG: 05:09:12.343: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 432s ** (umockdev-run:2192): DEBUG: 05:09:12.436: umockdev.vala:154: Removing test bed /tmp/umockdev.7MEL22 432s (umockdev-run:2192): GLib-DEBUG: 05:09:12.443: unsetenv() is not thread-safe and should not be used after threads are created 432s Comparing PNGs /tmp/libfprint-umockdev-test-2dx5cke_/capture.png and /usr/share/installed-tests/libfprint-2/vfs7552/capture.png 432s PASS: libfprint-2/driver-vfs7552.test 432s Running test: libfprint-2/driver-uru4000-4500.test 432s ** (umockdev-run:2205): DEBUG: 05:09:12.533: umockdev.vala:127: Created udev test bed /tmp/umockdev.TXG112 432s ** (umockdev-run:2205): DEBUG: 05:09:12.534: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 432s ** (umockdev-run:2205): DEBUG: 05:09:12.536: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 432s ** (umockdev-run:2205): DEBUG: 05:09:12.541: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TXG112/dev/bus/usb/001/050 432s ** (umockdev-run:2205): DEBUG: 05:09:12.541: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 432s ** (umockdev-run:2205): DEBUG: 05:09:12.542: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 432s ** (umockdev-run:2205): DEBUG: 05:09:12.549: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TXG112/dev/bus/usb/001/001 432s ** (umockdev-run:2205): DEBUG: 05:09:12.549: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 432s ** (umockdev-run:2205): DEBUG: 05:09:12.549: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 432s (process:2209): libfprint-context-DEBUG: 05:09:12.669: Initializing FpContext (libfprint version 1.94.9+tod1) 432s (process:2209): libfprint-tod-DEBUG: 05:09:12.669: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 432s (process:2209): libfprint-context-DEBUG: 05:09:12.672: No driver found for USB device 1D6B:0002 432s (process:2209): libfprint-device-DEBUG: 05:09:12.673: Device reported probe completion 432s (process:2209): libfprint-device-DEBUG: 05:09:12.673: Completing action FPI_DEVICE_ACTION_PROBE in idle! 432s (process:2209): libfprint-device-DEBUG: 05:09:12.673: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.677: Image device open completed 432s (process:2209): libfprint-device-DEBUG: 05:09:12.677: Device reported open completion 432s (process:2209): libfprint-device-DEBUG: 05:09:12.677: Completing action FPI_DEVICE_ACTION_OPEN in idle! 432s (process:2209): libfprint-device-DEBUG: 05:09:12.677: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 432s (process:2209): libfprint-device-DEBUG: 05:09:12.678: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.678: Activating image device 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.678: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.678: [uru4000] INIT_NUM_STATES entering state 0 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.678: read 1 regs at 7 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.679: reg value 1 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.679: [uru4000] INIT_NUM_STATES entering state 1 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.679: [uru4000] INIT_NUM_STATES entering state 3 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.679: set 81 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.679: [uru4000] INIT_NUM_STATES entering state 4 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.679: [uru4000] POWERUP_NUM_STATES entering state 0 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.679: [uru4000] POWERUP_NUM_STATES entering state 1 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.679: set 01 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.680: recv irq type 56aa 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.680: early scanpwr interrupt 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.680: [uru4000] POWERUP_NUM_STATES entering state 2 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.680: read 1 regs at 7 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.681: reg value 1 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.681: [uru4000] POWERUP_NUM_STATES entering state 3 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.681: [uru4000] POWERUP_NUM_STATES completed successfully 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.681: [uru4000] INIT_NUM_STATES entering state 5 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.681: [uru4000] INIT_NUM_STATES entering state 6 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.681: [uru4000] INIT_NUM_STATES entering state 7 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.681: read 16 regs at f0 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.681: reg value 1a 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.681: [uru4000] INIT_NUM_STATES entering state 8 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.681: Versions 0010 and 0115 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.681: [uru4000] INIT_NUM_STATES completed successfully 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.681: Image device activation completed 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.681: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.681: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.681: wait finger on 432s (process:2209): libfprint-device-DEBUG: 05:09:12.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.682: recv irq type 56aa 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.683: recv irq type 56aa 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.683: recv irq type 0101 432s (process:2209): libfprint-device-DEBUG: 05:09:12.683: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.684: Image device reported finger status: on 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.684: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.684: starting capture 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.684: Image encryption seed: 1374298404 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.684: [uru4000] IMAGING_NUM_STATES entering state 0 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.686: [uru4000] IMAGING_NUM_STATES entering state 1 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.686: hw header lines 289 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.686: dev2: 11240 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.686: image seems to be encrypted 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.686: [uru4000] IMAGING_NUM_STATES entering state 2 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.686: read 4 regs at 34 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: reg value f2 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.687: [uru4000] IMAGING_NUM_STATES entering state 3 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: encryption id 00 -> key 544409d6 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: 0 02 72 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: decoding 72 lines 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: 1 00 1 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: skipping 1 lines 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: 2 02 49 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: decoding 49 lines 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: 3 01 1 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: skipping 1 lines 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: 4 00 1 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: skipping 1 lines 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: 5 02 49 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: decoding 49 lines 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: 6 00 1 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: skipping 1 lines 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: 7 02 116 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.687: decoding 116 lines 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.688: [uru4000] IMAGING_NUM_STATES entering state 4 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.688: Image device captured an image 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.689: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 432s (process:2209): libfprint-device-DEBUG: 05:09:12.689: Device reported finger status change: FP_FINGER_STATUS_PRESENT 432s (process:2209): libfprint-SSM-DEBUG: 05:09:12.689: [uru4000] IMAGING_NUM_STATES completed successfully 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.689: await finger off 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.691: recv irq type 0200 432s (process:2209): libfprint-device-DEBUG: 05:09:12.691: Device reported finger status change: FP_FINGER_STATUS_NONE 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.691: Image device reported finger status: off 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.691: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.691: Deactivating image device 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.691: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.691: deactivating 432s (process:2209): libfprint-uru4000-DEBUG: 05:09:12.691: cancelled 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.692: Image device deactivation completed 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.692: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 432s (process:2209): libfprint-image-DEBUG: 05:09:12.717: Minutiae scan completed in 0.026947 secs 432s (process:2209): libfprint-device-DEBUG: 05:09:12.717: Device reported capture completion 432s (process:2209): libfprint-device-DEBUG: 05:09:12.717: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 432s (process:2209): libfprint-device-DEBUG: 05:09:12.717: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 432s (process:2209): libfprint-image_device-DEBUG: 05:09:12.718: Image device close completed 432s (process:2209): libfprint-device-DEBUG: 05:09:12.718: Device reported close completion 432s (process:2209): libfprint-device-DEBUG: 05:09:12.718: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 432s (process:2209): libfprint-device-DEBUG: 05:09:12.718: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 432s ** (umockdev-run:2205): DEBUG: 05:09:12.916: umockdev.vala:154: Removing test bed /tmp/umockdev.TXG112 432s (umockdev-run:2205): GLib-DEBUG: 05:09:12.926: unsetenv() is not thread-safe and should not be used after threads are created 432s Executing: libfprint-2/driver-uru4000-4500.test 433s Comparing PNGs /tmp/libfprint-umockdev-test-s0z0iygz/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-4500/capture.png 433s PASS: libfprint-2/driver-uru4000-4500.test 433s Running test: libfprint-2/driver-upektc_img-tcs1s.test 433s ** (umockdev-run:2218): DEBUG: 05:09:13.031: umockdev.vala:127: Created udev test bed /tmp/umockdev.IQKC22 433s ** (umockdev-run:2218): DEBUG: 05:09:13.031: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 433s ** (umockdev-run:2218): DEBUG: 05:09:13.037: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 (subsystem usb) 433s ** (umockdev-run:2218): DEBUG: 05:09:13.042: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IQKC22/dev/bus/usb/003/004 433s ** (umockdev-run:2218): DEBUG: 05:09:13.042: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 433s ** (umockdev-run:2218): DEBUG: 05:09:13.048: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 (subsystem usb) 433s ** (umockdev-run:2218): DEBUG: 05:09:13.052: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IQKC22/dev/bus/usb/003/001 433s ** (umockdev-run:2218): DEBUG: 05:09:13.052: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4 433s ** (umockdev-run:2218): DEBUG: 05:09:13.055: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4 (subsystem pci) 433s ** (umockdev-run:2218): DEBUG: 05:09:13.059: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1 433s ** (umockdev-run:2218): DEBUG: 05:09:13.060: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1 (subsystem pci) 433s (process:2222): libfprint-context-DEBUG: 05:09:13.178: Initializing FpContext (libfprint version 1.94.9+tod1) 433s (process:2222): libfprint-tod-DEBUG: 05:09:13.178: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 433s (process:2222): libfprint-context-DEBUG: 05:09:13.181: No driver found for USB device 1D6B:0002 433s (process:2222): libfprint-device-DEBUG: 05:09:13.182: Device reported probe completion 433s (process:2222): libfprint-device-DEBUG: 05:09:13.182: Completing action FPI_DEVICE_ACTION_PROBE in idle! 433s (process:2222): libfprint-device-DEBUG: 05:09:13.182: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.184: Image device open completed 433s (process:2222): libfprint-device-DEBUG: 05:09:13.184: Device reported open completion 433s (process:2222): libfprint-device-DEBUG: 05:09:13.184: Completing action FPI_DEVICE_ACTION_OPEN in idle! 433s (process:2222): libfprint-device-DEBUG: 05:09:13.184: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 433s (process:2222): libfprint-device-DEBUG: 05:09:13.184: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.184: Activating image device 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.184: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.184: [upektc_img] ACTIVATE_NUM_STATES entering state 0 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.185: [upektc_img] ACTIVATE_NUM_STATES entering state 1 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.185: [upektc_img] ACTIVATE_NUM_STATES entering state 2 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.186: [upektc_img] ACTIVATE_NUM_STATES entering state 3 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.186: [upektc_img] ACTIVATE_NUM_STATES entering state 4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.187: [upektc_img] ACTIVATE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.188: [upektc_img] ACTIVATE_NUM_STATES entering state 6 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.188: [upektc_img] ACTIVATE_NUM_STATES entering state 7 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.189: [upektc_img] ACTIVATE_NUM_STATES entering state 8 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.189: [upektc_img] ACTIVATE_NUM_STATES entering state 9 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.190: [upektc_img] ACTIVATE_NUM_STATES entering state 10 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.190: [upektc_img] ACTIVATE_NUM_STATES entering state 11 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.191: Sensor type : TCS1x, width x height: 256 x 360 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.191: [upektc_img] ACTIVATE_NUM_STATES completed successfully 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.191: Image device activation completed 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.191: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.191: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 433s (process:2222): libfprint-device-DEBUG: 05:09:13.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.191: [upektc_img] CAPTURE_NUM_STATES entering state 0 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.191: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.192: request completed, len: 0000 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.192: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.192: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.192: 18th byte is 0c 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.192: [upektc_img] CAPTURE_NUM_STATES entering state 3 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.193: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.193: request completed, len: 0000 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.193: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.194: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.194: 18th byte is 13 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.194: [upektc_img] CAPTURE_NUM_STATES entering state 3 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.195: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.195: request completed, len: 0000 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.195: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.196: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.196: 18th byte is 00 433s (process:2222): libfprint-device-DEBUG: 05:09:13.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.196: [upektc_img] CAPTURE_NUM_STATES entering state 3 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.196: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.197: request completed, len: 0000 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.197: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.197: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.197: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.197: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.197: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.198: request completed, len: 07c4 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.198: Image device reported finger status: on 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.198: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.198: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.198: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.199: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.199: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.199: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.199: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.199: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.199: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.200: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.201: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.201: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.201: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.201: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.201: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.201: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.202: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.202: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.202: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.202: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.202: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.203: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.203: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.204: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.204: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.204: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.204: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.204: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.205: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.205: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.205: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.206: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.206: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.206: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.206: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.206: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.207: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.207: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.208: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.208: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.208: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.208: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.208: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.208: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.209: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.209: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.209: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.209: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.209: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.210: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.210: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.211: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.211: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.211: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.211: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.211: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.212: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.212: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.212: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.213: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.213: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.213: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.213: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.214: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.214: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.214: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.215: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.215: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.215: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.215: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.215: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.215: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.216: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.216: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.216: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.216: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.216: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.217: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.217: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.218: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.218: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.218: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.218: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.218: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.219: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.219: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.219: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.220: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.220: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.220: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.220: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.220: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.220: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.221: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.222: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.222: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.222: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.222: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.222: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.222: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.223: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.223: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.223: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.223: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.223: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.224: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.224: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.224: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.225: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.225: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.225: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.225: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.226: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.226: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.226: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.227: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.227: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.227: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.227: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.227: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.227: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.228: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.229: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.229: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.229: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.229: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.229: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.229: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.230: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.230: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.230: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.230: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.230: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.231: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.231: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.232: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.232: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.232: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.232: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.232: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.233: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.233: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.233: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.234: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.234: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.234: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.234: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.235: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.235: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.235: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.236: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.236: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.236: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.236: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.236: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.236: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.237: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.237: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.237: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.237: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.238: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.238: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.238: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.239: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.239: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.239: response_size is 2052, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.239: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.239: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.240: request completed, len: 07c4 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.240: [upektc_img] CAPTURE_NUM_STATES entering state 5 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.240: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.241: request completed, len: 0040 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.241: response_size is 814, actual_length is 64 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.241: Waiting for rest of transfer 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.241: [upektc_img] CAPTURE_NUM_STATES entering state 1 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.242: request completed, len: 02ee 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.242: Image size is 51840 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.242: Image device captured an image 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.243: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 433s (process:2222): libfprint-device-DEBUG: 05:09:13.243: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2222): libfprint-device-DEBUG: 05:09:13.243: Device reported finger status change: FP_FINGER_STATUS_NONE 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.243: Image device reported finger status: off 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.243: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.243: Deactivating image device 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.243: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.243: [upektc_img] CAPTURE_NUM_STATES completed successfully 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.243: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.244: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 433s (process:2222): libfprint-SSM-DEBUG: 05:09:13.244: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 433s (process:2222): libfprint-upektc_img-DEBUG: 05:09:13.244: Deactivate completed 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.244: Image device deactivation completed 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.244: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 433s (process:2222): libfprint-image-DEBUG: 05:09:13.265: Minutiae scan completed in 0.022081 secs 433s (process:2222): libfprint-device-DEBUG: 05:09:13.265: Device reported capture completion 433s (process:2222): libfprint-device-DEBUG: 05:09:13.266: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 433s (process:2222): libfprint-device-DEBUG: 05:09:13.266: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 433s (process:2222): libfprint-image_device-DEBUG: 05:09:13.266: Image device close completed 433s (process:2222): libfprint-device-DEBUG: 05:09:13.266: Device reported close completion 433s (process:2222): libfprint-device-DEBUG: 05:09:13.267: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 433s (process:2222): libfprint-device-DEBUG: 05:09:13.267: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s ** (umockdev-run:2218): DEBUG: 05:09:13.372: umockdev.vala:154: Removing test bed /tmp/umockdev.IQKC22 433s (umockdev-run:2218): GLib-DEBUG: 05:09:13.381: unsetenv() is not thread-safe and should not be used after threads are created 433s Comparing PNGs /tmp/libfprint-umockdev-test-2yvrm4ba/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img-tcs1s/capture.png 433s PASS: libfprint-2/driver-upektc_img-tcs1s.test 433s Running test: libfprint-2/driver-egismoc.test 433s ** (umockdev-run:2231): DEBUG: 05:09:13.468: umockdev.vala:127: Created udev test bed /tmp/umockdev.IK0J22 433s ** (umockdev-run:2231): DEBUG: 05:09:13.468: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 433s ** (umockdev-run:2231): DEBUG: 05:09:13.470: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 433s ** (umockdev-run:2231): DEBUG: 05:09:13.475: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IK0J22/dev/bus/usb/003/012 433s ** (umockdev-run:2231): DEBUG: 05:09:13.476: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 433s ** (umockdev-run:2231): DEBUG: 05:09:13.477: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 433s ** (umockdev-run:2231): DEBUG: 05:09:13.481: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IK0J22/dev/bus/usb/003/001 433s ** (umockdev-run:2231): DEBUG: 05:09:13.481: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 433s ** (umockdev-run:2231): DEBUG: 05:09:13.482: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 433s (process:2235): libfprint-context-DEBUG: 05:09:13.598: Initializing FpContext (libfprint version 1.94.9+tod1) 433s (process:2235): libfprint-tod-DEBUG: 05:09:13.599: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.601: 131012595712: ../libfprint/drivers/egismoc/egismoc.c:1597 433s (process:2235): libfprint-context-DEBUG: 05:09:13.602: No driver found for USB device 1D6B:0002 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.602: egismoc_probe enter --> 433s (process:2235): libfprint-device-DEBUG: 05:09:13.604: Device reported probe completion 433s (process:2235): libfprint-device-DEBUG: 05:09:13.604: Completing action FPI_DEVICE_ACTION_PROBE in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.604: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.605: Opening device 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.606: [egismoc] DEV_INIT_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.607: [egismoc] DEV_INIT_STATES entering state 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.608: [egismoc] DEV_INIT_STATES entering state 2 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.609: [egismoc] DEV_INIT_STATES entering state 3 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.609: [egismoc] DEV_INIT_STATES entering state 4 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.611: [egismoc] DEV_INIT_STATES entering state 5 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.611: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.611: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.611: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.612: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.612: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.612: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.612: Firmware version callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.612: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.612: Device firmware version is 9050.1.1.81 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.612: [egismoc] DEV_INIT_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.612: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.612: Device reported open completion 433s (process:2235): libfprint-device-DEBUG: 05:09:13.612: Completing action FPI_DEVICE_ACTION_OPEN in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.612: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.613: List 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.613: [egismoc] LIST_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.613: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.613: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.613: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.614: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.614: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.614: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.614: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.614: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.614: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.614: Device fingerprint 3: FP1-20231016-3-5159A026-root 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.614: Device fingerprint 4: FP1-20231016-4-A25C1212-root 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.614: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.614: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.614: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.614: Number of currently enrolled fingerprints on the device is 7 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.614: [egismoc] LIST_STATES entering state 1 433s (process:2235): libfprint-device-DEBUG: 05:09:13.614: Device reported listing completion 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.614: [egismoc] LIST_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.614: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.614: Completing action FPI_DEVICE_ACTION_LIST in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.614: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.615: Clear storage 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.615: [egismoc] DELETE_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.615: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.615: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.615: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.615: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.616: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Device fingerprint 3: FP1-20231016-3-5159A026-root 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Device fingerprint 4: FP1-20231016-4-A25C1212-root 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Number of currently enrolled fingerprints on the device is 7 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.616: [egismoc] DELETE_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Get delete command 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.616: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.616: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.616: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.617: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.617: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.617: Delete callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.617: Response prefix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.617: Device reported deletion completion 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.617: [egismoc] DELETE_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.617: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.617: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.617: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.617: List 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.617: [egismoc] LIST_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.617: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.617: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.617: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.617: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.618: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.618: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.618: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.618: Number of currently enrolled fingerprints on the device is 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.618: [egismoc] LIST_STATES entering state 1 433s (process:2235): libfprint-device-DEBUG: 05:09:13.618: Device reported listing completion 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.618: [egismoc] LIST_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.618: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.618: Completing action FPI_DEVICE_ACTION_LIST in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.618: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 433s (process:2235): libfprint-device-DEBUG: 05:09:13.619: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.619: Enroll 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.619: [egismoc] ENROLL_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.619: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.619: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.619: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.620: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.621: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.621: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.621: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.621: Number of currently enrolled fingerprints on the device is 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.621: [egismoc] ENROLL_STATES entering state 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.621: [egismoc] ENROLL_STATES entering state 2 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.621: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.621: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.621: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.622: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.623: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.623: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.623: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.623: [egismoc] ENROLL_STATES entering state 3 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.623: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.623: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.623: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.624: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.625: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.625: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.625: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.625: [egismoc] ENROLL_STATES entering state 4 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.625: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.626: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.626: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.626: [egismoc] ENROLL_STATES entering state 5 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.626: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.626: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.626: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.626: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.627: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.627: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.627: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.627: [egismoc] ENROLL_STATES entering state 6 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.627: Get check command 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.627: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.627: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.627: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.628: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.628: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.628: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.628: Enroll check callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.628: Response suffix valid: yes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.628: [egismoc] ENROLL_STATES entering state 7 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.628: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.628: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.628: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.629: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.630: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.630: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.630: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.630: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.630: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.630: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.630: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.630: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.631: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.631: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.631: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.631: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.631: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.631: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.631: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.632: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.633: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.633: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.633: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.633: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.633: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.633: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.633: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.633: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.633: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.633: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.633: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.633: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.634: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.635: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.635: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.635: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.635: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.635: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.635: Partial capture successful. Please touch the sensor again (1/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.635: Device reported enroll progress, reported 1 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.635: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.635: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.635: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.635: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.635: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.636: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.636: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.636: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.636: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.636: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.636: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.636: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.637: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.638: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.638: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.638: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.638: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.638: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.638: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.638: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.638: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.638: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.638: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.638: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.638: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.639: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.640: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.640: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.640: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.640: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.640: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.640: Partial capture successful. Please touch the sensor again (2/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.640: Device reported enroll progress, reported 2 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.640: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.640: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.640: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.640: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.641: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.642: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.642: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.642: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.642: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.642: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.642: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.642: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.642: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.643: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.643: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.643: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.643: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.643: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.643: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.644: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.644: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.644: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.644: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.644: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.644: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.644: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.645: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.645: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.645: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.645: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.645: Response suffix valid: NO 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.645: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.645: Response suffix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.645: Device reported enroll progress, reported 2 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.645: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.645: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.645: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.645: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.646: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.646: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.646: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.647: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.647: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.647: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.647: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.647: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.647: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.648: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.648: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.648: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.648: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.648: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.648: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.649: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.649: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.649: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.649: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.649: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.649: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.649: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.650: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.650: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.650: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.650: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.650: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.650: Partial capture successful. Please touch the sensor again (3/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.650: Device reported enroll progress, reported 3 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.650: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.650: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.650: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.650: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.651: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.652: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.652: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.652: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.652: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.652: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.652: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.652: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.653: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.653: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.653: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.653: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.653: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.653: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.653: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.654: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.654: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.654: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.654: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.654: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.654: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.655: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.655: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.656: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.656: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.656: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.656: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.656: Partial capture successful. Please touch the sensor again (4/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.656: Device reported enroll progress, reported 4 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.656: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.656: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.656: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.656: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.656: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.657: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.657: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.657: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.657: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.657: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.657: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.657: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.658: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.659: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.659: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.659: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.659: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.659: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.659: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.659: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.659: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.659: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.659: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.659: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.660: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.661: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.661: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.661: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.661: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.661: Response suffix valid: NO 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.661: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.661: Response suffix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.661: Device reported enroll progress, reported 4 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.661: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.661: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.661: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.661: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.662: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.662: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.662: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.662: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.662: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.662: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.662: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.663: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.663: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.664: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.664: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.664: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.664: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.664: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.664: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.665: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.665: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.665: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.665: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.665: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.665: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.666: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.666: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.666: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.666: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.666: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.666: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.666: Partial capture successful. Please touch the sensor again (5/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.666: Device reported enroll progress, reported 5 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.666: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.666: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.666: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.666: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.667: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.668: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.668: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.668: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.668: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.668: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.668: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.668: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.669: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.669: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.669: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.669: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.669: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.669: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.670: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.670: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.670: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.670: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.670: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.670: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.670: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.671: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.672: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.672: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.672: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.672: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.672: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.672: Partial capture successful. Please touch the sensor again (6/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.672: Device reported enroll progress, reported 6 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.672: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.672: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.672: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.672: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.673: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.673: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.673: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.673: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.673: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.673: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.673: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.673: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.674: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.675: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.675: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.675: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.675: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.675: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.676: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.676: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.676: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.676: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.676: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.676: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.677: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.677: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.677: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.677: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.677: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.677: Response suffix valid: NO 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.677: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.677: Response suffix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.677: Device reported enroll progress, reported 6 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.677: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.677: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.677: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.677: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.678: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.679: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.679: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.679: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.679: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.679: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.679: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.679: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.680: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.680: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.681: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.681: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.681: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.681: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.681: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.681: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.681: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.681: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.681: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.681: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.682: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.683: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.683: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.683: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.683: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.683: Response suffix valid: NO 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.683: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.683: Response suffix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.683: Device reported enroll progress, reported 6 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.683: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.683: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.683: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.683: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.684: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.684: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.684: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.684: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.684: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.684: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.685: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.685: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.685: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.686: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.686: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.686: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.686: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.686: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.686: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.687: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.687: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.687: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.687: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.687: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.687: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.688: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.688: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.688: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.688: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.688: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.688: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.688: Partial capture successful. Please touch the sensor again (7/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.688: Device reported enroll progress, reported 7 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.688: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.688: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.688: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.688: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.689: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.690: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.690: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.690: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.690: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.690: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.690: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.690: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.691: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.691: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.691: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.691: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.691: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.691: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.691: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.692: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.692: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.692: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.692: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.692: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.692: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.693: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.694: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.694: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.694: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.694: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.694: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.694: Partial capture successful. Please touch the sensor again (8/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.694: Device reported enroll progress, reported 8 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.694: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.694: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.694: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.694: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.695: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.696: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.696: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.696: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.696: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.696: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.696: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.696: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.696: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.697: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.697: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.697: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.697: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.697: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.697: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.698: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.698: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.698: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.698: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.698: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.698: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.699: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.700: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.700: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.700: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.700: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.700: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.700: Partial capture successful. Please touch the sensor again (9/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.700: Device reported enroll progress, reported 9 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.700: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.700: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.700: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.700: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.701: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.701: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.701: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.701: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.701: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.701: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.701: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.701: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.702: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.703: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.703: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.703: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.703: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.703: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.703: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.703: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.703: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.703: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.703: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.703: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.704: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.704: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.705: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.705: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.705: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.705: Response suffix valid: NO 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.705: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.705: Response suffix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.705: Device reported enroll progress, reported 9 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.705: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.705: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.705: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.705: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.705: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.706: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.706: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.706: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.706: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.706: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.706: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.706: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.707: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.708: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.708: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.708: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.708: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.708: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.708: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.708: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.708: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.708: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.708: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.708: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.708: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.709: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.710: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.710: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.710: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.710: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.710: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.710: Partial capture successful. Please touch the sensor again (10/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.710: Device reported enroll progress, reported 10 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.710: [egismoc] ENROLL_STATES entering state 12 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.710: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.710: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.710: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.710: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.711: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.711: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.711: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.711: [egismoc] ENROLL_STATES entering state 13 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.711: New fingerprint ID: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.711: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.711: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.711: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.712: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.713: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.713: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.713: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.713: [egismoc] ENROLL_STATES entering state 14 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.713: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.713: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.713: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.713: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.714: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.714: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.714: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.714: [egismoc] ENROLL_STATES entering state 15 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.714: Enrollment was successful! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.714: Device reported enroll completion 433s (process:2235): libfprint-device-DEBUG: 05:09:13.714: Device reported finger status change: FP_FINGER_STATUS_NONE 433s (process:2235): libfprint-device-DEBUG: 05:09:13.714: Print for finger FP_FINGER_LEFT_INDEX enrolled 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.714: [egismoc] ENROLL_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.714: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.714: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.714: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.715: List 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.715: [egismoc] LIST_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.715: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.715: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.715: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.715: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.716: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.716: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.716: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.716: Device fingerprint 1: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.716: Number of currently enrolled fingerprints on the device is 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.716: [egismoc] LIST_STATES entering state 1 433s (process:2235): libfprint-device-DEBUG: 05:09:13.716: Device reported listing completion 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.716: [egismoc] LIST_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.716: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.716: Completing action FPI_DEVICE_ACTION_LIST in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.716: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-device-DEBUG: 05:09:13.717: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.717: Identify or Verify 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.717: [egismoc] IDENTIFY_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.717: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.717: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.717: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.718: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.718: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.718: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.718: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.718: Device fingerprint 1: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.718: Number of currently enrolled fingerprints on the device is 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.718: [egismoc] IDENTIFY_STATES entering state 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.718: [egismoc] IDENTIFY_STATES entering state 2 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.718: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.718: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.718: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.719: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.720: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.720: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.720: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.720: [egismoc] IDENTIFY_STATES entering state 3 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.720: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.720: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.720: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.721: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.721: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.721: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.721: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.721: [egismoc] IDENTIFY_STATES entering state 4 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.721: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.722: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.722: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.722: [egismoc] IDENTIFY_STATES entering state 5 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.722: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.722: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.722: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.722: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.723: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.723: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.723: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.723: [egismoc] IDENTIFY_STATES entering state 6 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.723: Get check command 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.723: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.723: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.723: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.724: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.725: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.725: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.725: Identify check callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.725: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.725: Identify successful for: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.725: Verifying against: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-device-DEBUG: 05:09:13.725: Device reported verify result 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.725: [egismoc] IDENTIFY_STATES entering state 7 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.725: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.725: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.725: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.725: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.726: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.726: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.726: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.726: [egismoc] IDENTIFY_STATES entering state 8 433s (process:2235): libfprint-device-DEBUG: 05:09:13.726: Device reported verify completion 433s (process:2235): libfprint-device-DEBUG: 05:09:13.726: Device reported finger status change: FP_FINGER_STATUS_NONE 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.726: [egismoc] IDENTIFY_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.726: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.726: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.726: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-device-DEBUG: 05:09:13.727: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.727: Identify or Verify 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.727: [egismoc] IDENTIFY_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.727: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.727: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.728: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.728: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.729: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.729: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.729: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.729: Device fingerprint 1: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.729: Number of currently enrolled fingerprints on the device is 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.729: [egismoc] IDENTIFY_STATES entering state 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.729: [egismoc] IDENTIFY_STATES entering state 2 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.729: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.729: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.729: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.730: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.731: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.731: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.731: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.731: [egismoc] IDENTIFY_STATES entering state 3 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.731: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.731: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.731: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.731: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.732: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.732: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.732: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.732: [egismoc] IDENTIFY_STATES entering state 4 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.732: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.732: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.732: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.732: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.732: [egismoc] IDENTIFY_STATES entering state 5 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.732: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.732: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.732: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.733: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.734: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.734: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.734: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.734: [egismoc] IDENTIFY_STATES entering state 6 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.734: Get check command 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.734: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.734: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.734: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.735: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.735: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.735: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.735: Identify check callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.735: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.735: Identify successful for: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-device-DEBUG: 05:09:13.735: Device reported identify result 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.735: [egismoc] IDENTIFY_STATES entering state 7 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.735: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.735: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.735: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.736: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.737: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.737: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.737: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.737: [egismoc] IDENTIFY_STATES entering state 8 433s (process:2235): libfprint-device-DEBUG: 05:09:13.737: Device reported identify completion 433s (process:2235): libfprint-device-DEBUG: 05:09:13.737: Device reported finger status change: FP_FINGER_STATUS_NONE 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.737: [egismoc] IDENTIFY_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.737: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.737: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.737: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-device-DEBUG: 05:09:13.738: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.738: Enroll 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.738: [egismoc] ENROLL_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.738: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.738: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.738: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.739: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.740: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.740: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.740: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.740: Device fingerprint 1: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.740: Number of currently enrolled fingerprints on the device is 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.740: [egismoc] ENROLL_STATES entering state 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.740: [egismoc] ENROLL_STATES entering state 2 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.740: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.740: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.740: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.741: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.741: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.741: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.741: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.741: [egismoc] ENROLL_STATES entering state 3 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.741: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.741: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.741: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.742: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.743: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.743: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.743: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.743: [egismoc] ENROLL_STATES entering state 4 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.743: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.743: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.743: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.743: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.743: [egismoc] ENROLL_STATES entering state 5 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.743: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.743: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.743: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.744: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.745: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.745: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.745: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.745: [egismoc] ENROLL_STATES entering state 6 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.745: Get check command 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.745: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.745: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.745: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.745: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.746: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.746: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.746: Enroll check callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.746: Response suffix valid: NO 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.746: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.746: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.746: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.746: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 433s (process:2235): libfprint-device-DEBUG: 05:09:13.746: Device reported enroll completion 433s (process:2235): libfprint-device-DEBUG: 05:09:13.746: Device reported finger status change: FP_FINGER_STATUS_NONE 433s (process:2235): libfprint-device-DEBUG: 05:09:13.746: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.746: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.747: List 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.747: [egismoc] LIST_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.747: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.747: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.747: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.748: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.749: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.749: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.749: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.749: Device fingerprint 1: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.749: Number of currently enrolled fingerprints on the device is 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.749: [egismoc] LIST_STATES entering state 1 433s (process:2235): libfprint-device-DEBUG: 05:09:13.749: Device reported listing completion 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.749: [egismoc] LIST_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.749: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.749: Completing action FPI_DEVICE_ACTION_LIST in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.749: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-device-DEBUG: 05:09:13.749: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.749: Enroll 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.749: [egismoc] ENROLL_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.749: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.749: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.749: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.750: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.751: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.751: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.751: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.751: Device fingerprint 1: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.751: Number of currently enrolled fingerprints on the device is 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.751: [egismoc] ENROLL_STATES entering state 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.751: [egismoc] ENROLL_STATES entering state 2 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.751: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.751: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.751: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.751: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.752: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.752: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.752: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.752: [egismoc] ENROLL_STATES entering state 3 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.752: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.752: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.752: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.753: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.753: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.753: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.753: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.753: [egismoc] ENROLL_STATES entering state 4 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.753: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.754: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.754: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.754: [egismoc] ENROLL_STATES entering state 5 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.754: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.754: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.754: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.755: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.755: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.755: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.755: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.755: [egismoc] ENROLL_STATES entering state 6 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.755: Get check command 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.755: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.755: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.755: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.756: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.757: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.757: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.757: Enroll check callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.757: Response suffix valid: yes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.757: [egismoc] ENROLL_STATES entering state 7 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.757: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.757: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.757: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.757: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.758: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.758: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.758: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.758: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.758: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.758: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.758: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.758: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.759: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.759: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.759: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.759: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.759: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.759: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.759: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.760: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.761: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.761: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.761: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.761: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.761: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.761: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.761: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.761: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.761: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.761: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.761: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.761: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.762: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.763: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.763: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.763: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.763: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.763: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.763: Partial capture successful. Please touch the sensor again (1/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.763: Device reported enroll progress, reported 1 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.763: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.763: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.763: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.763: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.764: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.765: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.765: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.765: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.765: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.765: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.765: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.765: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.765: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.766: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.766: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.766: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.766: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.766: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.767: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.767: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.767: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.767: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.767: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.767: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.767: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.768: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.768: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.768: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.768: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.768: Response suffix valid: NO 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.768: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.768: Response suffix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.768: Device reported enroll progress, reported 1 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.768: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.768: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.768: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.768: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.769: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.770: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.770: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.770: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.770: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.770: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.770: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.770: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.770: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.771: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.771: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.771: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.771: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.771: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.771: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.772: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.772: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.772: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.772: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.772: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.772: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.772: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.773: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.773: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.773: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.773: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.773: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.773: Partial capture successful. Please touch the sensor again (2/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.773: Device reported enroll progress, reported 2 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.773: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.773: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.773: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.773: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.774: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.775: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.775: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.775: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.775: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.775: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.775: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.775: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.775: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.776: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.776: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.776: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.776: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.776: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.776: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.777: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.777: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.777: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.777: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.777: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.777: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.777: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.778: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.778: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.778: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.778: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.778: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.778: Partial capture successful. Please touch the sensor again (3/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.778: Device reported enroll progress, reported 3 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.778: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.778: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.778: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.778: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.779: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.780: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.780: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.780: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.780: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.780: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.780: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.780: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.780: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.781: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.781: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.781: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.781: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.781: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.782: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.782: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.782: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.782: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.782: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.782: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.782: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.783: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.783: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.783: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.783: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.783: Response suffix valid: NO 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.783: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.783: Response suffix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.783: Device reported enroll progress, reported 3 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.783: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.783: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.783: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.783: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.784: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.785: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.785: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.785: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.785: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.785: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.785: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.785: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.786: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.786: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.786: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.786: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.786: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.786: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.786: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.787: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.787: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.787: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.787: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.787: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.787: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.788: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.789: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.789: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.789: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.789: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.789: Response suffix valid: NO 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.789: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.789: Response suffix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.789: Device reported enroll progress, reported 3 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.789: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.789: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.789: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.789: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.790: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.791: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.791: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.791: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.791: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.791: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.791: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.791: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.791: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.792: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.792: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.792: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.792: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.792: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.792: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.793: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.793: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.793: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.793: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.793: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.793: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.793: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.794: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.794: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.794: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.794: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.794: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.794: Partial capture successful. Please touch the sensor again (4/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.794: Device reported enroll progress, reported 4 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.794: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.794: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.794: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.794: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.796: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.797: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.797: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.797: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.797: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.797: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.797: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.797: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.797: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.798: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.798: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.798: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.798: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.798: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.798: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.799: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.799: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.799: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.799: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.799: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.799: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.799: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.800: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.800: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.800: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.800: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.800: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.800: Partial capture successful. Please touch the sensor again (5/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.800: Device reported enroll progress, reported 5 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.800: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.800: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.800: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.800: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.801: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.802: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.802: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.802: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.802: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.802: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.802: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.802: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.802: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.803: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.803: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.803: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.803: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.803: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.804: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.804: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.804: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.804: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.804: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.804: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.804: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.805: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.805: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.805: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.805: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.805: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.805: Partial capture successful. Please touch the sensor again (6/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.805: Device reported enroll progress, reported 6 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.805: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.805: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.805: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.805: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.806: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.807: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.807: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.807: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.807: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.807: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.807: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.807: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.807: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.808: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.808: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.808: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.808: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.808: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.808: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.808: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.809: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.809: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.809: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.809: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.809: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.809: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.810: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.810: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.810: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.810: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.810: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.810: Partial capture successful. Please touch the sensor again (7/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.810: Device reported enroll progress, reported 7 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.810: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.810: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.810: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.810: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.811: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.811: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.811: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.811: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.811: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.811: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.811: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.812: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.812: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.813: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.813: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.813: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.813: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.813: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.813: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.813: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.813: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.813: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.813: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.813: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.814: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.815: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.815: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.815: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.815: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.815: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.815: Partial capture successful. Please touch the sensor again (8/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.815: Device reported enroll progress, reported 8 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.815: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.815: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.815: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.815: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.816: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.816: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.816: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.816: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.816: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.816: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.816: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.817: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.817: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.818: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.818: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.818: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.818: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.818: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.818: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.818: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.818: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.818: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.819: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.819: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.819: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.819: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.820: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.820: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.820: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.820: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.820: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.820: Partial capture successful. Please touch the sensor again (9/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.820: Device reported enroll progress, reported 9 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.820: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.820: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.820: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.820: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.821: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.821: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.821: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.821: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.821: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.821: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.821: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.821: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.822: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.823: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.823: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.823: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.823: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.823: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.823: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.823: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.823: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.823: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.823: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.823: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.823: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.824: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.825: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.825: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.825: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.825: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.825: Response suffix valid: NO 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.825: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.825: Response suffix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.825: Device reported enroll progress, reported 9 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.825: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.825: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.825: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.825: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.826: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.827: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.827: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.827: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.827: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.827: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.827: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.827: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.827: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.828: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.828: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.828: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.828: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.828: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.828: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.829: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.829: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.829: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.829: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.829: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.829: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.829: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.830: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.830: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.830: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.830: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.830: Response suffix valid: NO 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.830: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.830: Response suffix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.830: Device reported enroll progress, reported 9 of 10 have been completed 433s listing - device should have prints 433s clear device storage 433s clear done 433s listing - device should be empty 433s enrolling 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 1, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 2, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 3, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 4, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 4, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 5, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 6, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 7, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 8, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 9, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 10, , None, None) 433s enroll done 433s listing - device should have 1 print 433s verifying 433s verify done 433s async identifying 433s indentification_done: 433s try to enroll duplicate 433s duplicate enroll attempt done 433s listing - device should still only have 1 print 433s enroll new finger 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 1, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 1, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 2, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 3, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 4, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 5, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 6, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 7, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 8, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 9, , None, None) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))(process:2235): libfprint-SSM-DEBUG: 05:09:13.830: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.830: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.830: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.831: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.831: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.832: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.832: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.832: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.832: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.832: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.832: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.832: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.832: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.833: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.833: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.833: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.833: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.833: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.833: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.834: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.834: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.834: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.834: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.834: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.834: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.834: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.835: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.835: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.835: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.835: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.835: Response suffix valid: NO 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.835: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.835: Response suffix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.835: Device reported enroll progress, reported 9 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.835: [egismoc] ENROLL_STATES entering state 8 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.835: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.835: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.835: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.836: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.837: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.837: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.837: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.837: [egismoc] ENROLL_STATES entering state 9 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.837: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.837: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.837: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.837: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.838: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.838: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.838: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.838: [egismoc] ENROLL_STATES entering state 10 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.838: Wait for finger on sensor 433s (process:2235): libfprint-device-DEBUG: 05:09:13.838: Device reported finger status change: FP_FINGER_STATUS_NEEDED 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.839: Finger on sensor callback 433s (process:2235): libfprint-device-DEBUG: 05:09:13.839: Device reported finger status change: FP_FINGER_STATUS_PRESENT 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.839: [egismoc] ENROLL_STATES entering state 11 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.839: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.839: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.839: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.839: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.840: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.840: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.840: Read capture callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.840: Response prefix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.840: Response suffix valid: yes 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.840: Partial capture successful. Please touch the sensor again (10/10) 433s (process:2235): libfprint-device-DEBUG: 05:09:13.840: Device reported enroll progress, reported 10 of 10 have been completed 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.840: [egismoc] ENROLL_STATES entering state 12 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.840: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.840: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.840: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.841: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.841: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.841: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.841: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.841: [egismoc] ENROLL_STATES entering state 13 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.842: New fingerprint ID: FP1-00000000-7-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.842: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.842: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.842: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.842: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.843: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.843: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.843: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.843: [egismoc] ENROLL_STATES entering state 14 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.843: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.843: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.843: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.844: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.844: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.844: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.844: Task SSM next state callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.844: [egismoc] ENROLL_STATES entering state 15 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.844: Enrollment was successful! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.844: Device reported enroll completion 433s (process:2235): libfprint-device-DEBUG: 05:09:13.844: Device reported finger status change: FP_FINGER_STATUS_NONE 433s (process:2235): libfprint-device-DEBUG: 05:09:13.844: Print for finger FP_FINGER_RIGHT_INDEX enrolled 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.844: [egismoc] ENROLL_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.844: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.844: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.844: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.844: List 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.844: [egismoc] LIST_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.844: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.844: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.845: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.845: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.846: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.846: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.846: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.846: Device fingerprint 1: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.846: Device fingerprint 2: FP1-00000000-7-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.846: Number of currently enrolled fingerprints on the device is 2 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.846: [egismoc] LIST_STATES entering state 1 433s (process:2235): libfprint-device-DEBUG: 05:09:13.846: Device reported listing completion 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.846: [egismoc] LIST_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.846: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.846: Completing action FPI_DEVICE_ACTION_LIST in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.846: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.846: Delete 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.846: [egismoc] DELETE_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.846: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.846: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.846: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.847: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.848: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.848: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.848: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.848: Device fingerprint 1: FP1-00000000-2-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.848: Device fingerprint 2: FP1-00000000-7-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.848: Number of currently enrolled fingerprints on the device is 2 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.848: [egismoc] DELETE_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.848: Get delete command 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.848: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.848: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.848: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.848: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.849: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.849: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.849: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.849: Delete callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.849: Response prefix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.849: Device reported deletion completion 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.849: [egismoc] DELETE_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.849: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.849: Completing action FPI_DEVICE_ACTION_DELETE in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.849: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.850: List 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.850: [egismoc] LIST_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.850: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.850: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.850: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.850: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.851: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.851: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.851: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.851: Device fingerprint 1: FP1-00000000-7-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.851: Number of currently enrolled fingerprints on the device is 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.851: [egismoc] LIST_STATES entering state 1 433s (process:2235): libfprint-device-DEBUG: 05:09:13.851: Device reported listing completion 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.851: [egismoc] LIST_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.851: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.851: Completing action FPI_DEVICE_ACTION_LIST in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.851: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.851: Clear storage 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.851: [egismoc] DELETE_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.851: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.851: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.851: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.852: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.853: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.853: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.853: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.853: Device fingerprint 1: FP1-00000000-7-00000000-nobody 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.853: Number of currently enrolled fingerprints on the device is 1 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.853: [egismoc] DELETE_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.853: Get delete command 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.853: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.853: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.853: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.853: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.854: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.854: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.854: Delete callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.854: Response prefix valid: yes 433s (process:2235): libfprint-device-DEBUG: 05:09:13.854: Device reported deletion completion 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.854: [egismoc] DELETE_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.854: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.854: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.854: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.854: List 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.854: [egismoc] LIST_STATES entering state 0 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.854: Execute command and get response 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.854: Get check bytes 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.854: [egismoc] CMD_STATES entering state 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.855: [egismoc] CMD_STATES entering state 1 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.856: Command receive callback 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.856: [egismoc] CMD_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.856: List callback 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.856: Number of currently enrolled fingerprints on the device is 0 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.856: [egismoc] LIST_STATES entering state 1 433s (process:2235): libfprint-device-DEBUG: 05:09:13.856: Device reported listing completion 433s (process:2235): libfprint-SSM-DEBUG: 05:09:13.856: [egismoc] LIST_STATES completed successfully 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.856: Task SSM done 433s (process:2235): libfprint-device-DEBUG: 05:09:13.856: Completing action FPI_DEVICE_ACTION_LIST in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.856: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.856: Closing device 433s (process:2235): libfprint-egismoc-DEBUG: 05:09:13.856: Cancel 433s (process:2235): libfprint-device-DEBUG: 05:09:13.856: Device reported close completion 433s (process:2235): libfprint-device-DEBUG: 05:09:13.856: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 433s (process:2235): libfprint-device-DEBUG: 05:09:13.857: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 433s 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 433s finger status: 433s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe7b40b28 (FpiDeviceEgisMoc at 0x12a8fc8)>, 10, , None, None) 433s enroll new finger done 433s listing - device should have 2 prints 433s deleting first print 433s delete done 433s listing - device should only have second print 433s clear device storage 433s clear done 433s listing - device should be empty 433s ** (umockdev-run:2231): DEBUG: 05:09:13.938: umockdev.vala:154: Removing test bed /tmp/umockdev.IK0J22 433s (umockdev-run:2231): GLib-DEBUG: 05:09:13.946: unsetenv() is not thread-safe and should not be used after threads are created 433s PASS: libfprint-2/driver-egismoc.test 433s Running test: libfprint-2/driver-synaptics.test 434s ** (umockdev-run:2243): DEBUG: 05:09:14.016: umockdev.vala:127: Created udev test bed /tmp/umockdev.DTVC22 434s ** (umockdev-run:2243): DEBUG: 05:09:14.016: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 434s ** (umockdev-run:2243): DEBUG: 05:09:14.018: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 434s ** (umockdev-run:2243): DEBUG: 05:09:14.022: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DTVC22/dev/bus/usb/001/004 434s ** (umockdev-run:2243): DEBUG: 05:09:14.022: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 434s ** (umockdev-run:2243): DEBUG: 05:09:14.023: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 434s ** (umockdev-run:2243): DEBUG: 05:09:14.027: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DTVC22/dev/bus/usb/001/001 434s ** (umockdev-run:2243): DEBUG: 05:09:14.027: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 434s ** (umockdev-run:2243): DEBUG: 05:09:14.028: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 434s (process:2247): libfprint-context-DEBUG: 05:09:14.149: Initializing FpContext (libfprint version 1.94.9+tod1) 434s (process:2247): libfprint-tod-DEBUG: 05:09:14.149: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 434s (process:2247): libfprint-context-DEBUG: 05:09:14.152: No driver found for USB device 1D6B:0002 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.153: 131013146824: ../libfprint/drivers/synaptics/synaptics.c:1247 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.155: Build Time: 1596608839 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.155: Build Num: 3273255 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.155: Version: 10.1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.155: Target: 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.155: Product: 65 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.155: sequence number is 1 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.155: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.156: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.157: Device reported probe completion 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.157: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 434s (process:2247): libfprint-device-DEBUG: 05:09:14.157: Completing action FPI_DEVICE_ACTION_PROBE in idle! 434s (process:2247): libfprint-device-DEBUG: 05:09:14.157: Not updating temperature model, device can run continuously! 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.159: 131013153376: ../libfprint/drivers/synaptics/synaptics.c:1407 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.159: sequence number is 2 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.159: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.160: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.161: Device reported open completion 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.161: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 434s (process:2247): libfprint-device-DEBUG: 05:09:14.161: Completing action FPI_DEVICE_ACTION_OPEN in idle! 434s (process:2247): libfprint-device-DEBUG: 05:09:14.161: Not updating temperature model, device can run continuously! 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.161: clear all prints in database 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.161: sequence number is 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.161: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.162: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.163: Deleting All Enrolled Users is 0% complete 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.163: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.163: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.163: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.164: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.164: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.164: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.165: Deleting All Enrolled Users is 100% complete 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.165: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.165: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.165: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.166: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.166: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.166: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.167: Successfully deleted all enrolled user 434s (process:2247): libfprint-device-DEBUG: 05:09:14.167: Device reported deletion completion 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.167: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 434s (process:2247): libfprint-device-DEBUG: 05:09:14.167: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 434s (process:2247): libfprint-device-DEBUG: 05:09:14.167: Not updating temperature model, device can run continuously! 434s (process:2247): libfprint-device-DEBUG: 05:09:14.168: Not updating temperature model, device can run continuously! 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.168: 131013162120: ../libfprint/drivers/synaptics/synaptics.c:1018 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.168: user_id: FP1-00000000-0-00000000-nobody, finger: 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.168: sequence number is 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.168: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.169: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.169: Place Finger on the Sensor! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.169: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.170: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.170: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.171: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.171: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.171: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.171: Finger is now on the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.171: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.171: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.172: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.172: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.172: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.173: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.173: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.173: Fingerprint image capture complete! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.173: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.174: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.174: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.175: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.175: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.175: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.175: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.175: Finger is now off the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.175: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.175: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.176: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.176: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.177: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.177: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.177: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.177: Enrollment is 12 % 434s (process:2247): libfprint-device-DEBUG: 05:09:14.177: Device reported enroll progress, reported 1 of 8 have been completed 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.177: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.178: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.178: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.179: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.179: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.179: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.179: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.179: Finger is now on the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.180: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.180: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.180: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.180: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.181: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.181: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.181: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.182: Fingerprint image capture complete! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.182: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.182: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.182: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.183: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.183: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.183: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.184: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.184: Finger is now off the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.184: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.184: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.184: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.184: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.185: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.185: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.185: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.186: Enrollment is 25 % 434s (process:2247): libfprint-device-DEBUG: 05:09:14.186: Device reported enroll progress, reported 2 of 8 have been completed 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.186: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.186: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.186: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.187: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.187: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.187: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.188: Finger is now on the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.188: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.188: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.189: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.189: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.189: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.189: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.189: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.190: Fingerprint image capture complete! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.190: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.190: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.190: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.191: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.191: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.191: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.192: Enrollment is 37 % 434s (process:2247): libfprint-device-DEBUG: 05:09:14.192: Device reported enroll progress, reported 3 of 8 have been completed 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.192: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.193: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.193: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.193: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.193: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.193: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.194: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.194: Finger is now off the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.194: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.194: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.195: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.195: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.195: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.195: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.195: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.196: Finger is now on the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.196: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.196: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.197: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.197: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.197: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.197: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.197: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.198: Fingerprint image capture complete! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.198: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.198: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.198: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.199: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.199: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.199: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.200: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.200: Finger is now off the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.200: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.200: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.200: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.201: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.202: Enrollment is 50 % 434s (process:2247): libfprint-device-DEBUG: 05:09:14.202: Device reported enroll progress, reported 4 of 8 have been completed 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.202: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.203: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.203: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.203: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.203: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.203: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.204: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.204: Finger is now on the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.204: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.204: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.205: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.206: Fingerprint image capture complete! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.206: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.207: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.207: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.207: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.207: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.207: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.208: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.208: Finger is now off the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.208: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.208: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.209: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.209: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.209: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.209: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.209: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.210: Enrollment is 62 % 434s (process:2247): libfprint-device-DEBUG: 05:09:14.210: Device reported enroll progress, reported 5 of 8 have been completed 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.210: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.211: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.211: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.212: Finger is now on the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.212: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.212: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.213: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.213: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.213: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.213: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.213: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.214: Fingerprint image capture complete! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.214: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.215: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.215: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.215: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.215: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.215: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.216: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.216: Finger is now off the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.216: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.216: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.217: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.217: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.217: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.217: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.217: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.218: Enrollment is 62 % 434s (process:2247): libfprint-device-DEBUG: 05:09:14.218: Device reported enroll progress, reported 5 of 8 have been completed 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.218: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.219: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.219: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.219: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.219: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.219: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.220: Finger is now on the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.220: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.220: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.221: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.221: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.221: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.221: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.221: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.222: Fingerprint image capture complete! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.222: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.223: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.223: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.223: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.223: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.223: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.224: Enrollment is 75 % 434s (process:2247): libfprint-device-DEBUG: 05:09:14.224: Device reported enroll progress, reported 6 of 8 have been completed 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.224: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.225: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.225: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.225: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.226: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.226: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.226: Finger is now off the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.226: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.226: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.227: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.227: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.227: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.227: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.227: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.228: Finger is now on the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.228: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.228: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.229: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.229: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.230: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.230: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.230: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.230: Fingerprint image capture complete! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.230: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.231: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.231: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.232: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.232: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.232: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.232: Finger is now off the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.232: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.232: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.233: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.233: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.234: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.234: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.234: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.234: Enrollment is 87 % 434s (process:2247): libfprint-device-DEBUG: 05:09:14.234: Device reported enroll progress, reported 7 of 8 have been completed 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.234: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.235: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.235: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.236: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.236: Finger is now on the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.236: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.237: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.238: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.238: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.238: Fingerprint image capture complete! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.238: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.239: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.240: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.240: Finger is now off the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.240: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.240: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.241: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.241: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.241: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.241: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.241: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.242: Enrollment is 100 % 434s (process:2247): libfprint-device-DEBUG: 05:09:14.242: Device reported enroll progress, reported 8 of 8 have been completed 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.242: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.243: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.243: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.243: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.243: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.243: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.244: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.244: Finger is now on the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.244: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.244: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.245: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.246: Finger is now off the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.246: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.246: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.247: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.247: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.247: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.247: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.247: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.248: Enrollment was successful! 434s (process:2247): libfprint-device-DEBUG: 05:09:14.248: Device reported enroll completion 434s (process:2247): libfprint-device-DEBUG: 05:09:14.248: Device reported finger status change: FP_FINGER_STATUS_NONE 434s (process:2247): libfprint-device-DEBUG: 05:09:14.248: Print for finger FP_FINGER_UNKNOWN enrolled 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.248: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 434s (process:2247): libfprint-device-DEBUG: 05:09:14.248: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 434s (process:2247): libfprint-device-DEBUG: 05:09:14.248: Not updating temperature model, device can run continuously! 434s (process:2247): libfprint-device-DEBUG: 05:09:14.248: Not updating temperature model, device can run continuously! 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.248: data is 0xf05600 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.248: 131013242649: ../libfprint/drivers/synaptics/synaptics.c:650 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.248: sequence number is 5 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.248: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.249: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.250: Place Finger on the Sensor! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.250: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.250: got suspend request 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.250: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.250: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 5 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.251: got resume request 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.251: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 6 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.251: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.252: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.252: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.253: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.253: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.253: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.253: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.253: Finger is now on the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.253: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.253: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.254: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.254: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.255: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.255: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.255: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.255: Fingerprint image capture complete! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.255: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.256: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.256: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.257: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.257: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.257: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-device-DEBUG: 05:09:14.257: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.257: Finger is now off the sensor 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.257: Received message with 0 sequence number 0x91, ignoring! 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.257: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.258: interrupt transfer done 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.258: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.259: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 61.800000 434s (process:2247): libfprint-device-DEBUG: 05:09:14.259: Device reported verify result 434s (process:2247): libfprint-device-DEBUG: 05:09:14.259: Device reported verify completion 434s (process:2247): libfprint-device-DEBUG: 05:09:14.259: Device reported finger status change: FP_FINGER_STATUS_NONE 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.259: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 434s (process:2247): libfprint-device-DEBUG: 05:09:14.259: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 434s (process:2247): libfprint-device-DEBUG: 05:09:14.259: Not updating temperature model, device can run continuously! 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.260: data is 0xf05600 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.260: 131013253884: ../libfprint/drivers/synaptics/synaptics.c:1127 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.260: sequence number is 6 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.260: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.260: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.261: Successfully deleted enrolled user 434s (process:2247): libfprint-device-DEBUG: 05:09:14.261: Device reported deletion completion 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.261: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 434s (process:2247): libfprint-device-DEBUG: 05:09:14.261: Completing action FPI_DEVICE_ACTION_DELETE in idle! 434s (process:2247): libfprint-device-DEBUG: 05:09:14.261: Not updating temperature model, device can run continuously! 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.261: 131013255256: ../libfprint/drivers/synaptics/synaptics.c:1428 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.261: sequence number is 7 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.261: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.262: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 434s (process:2247): libfprint-synaptics-DEBUG: 05:09:14.263: Fingerprint sensor ready to be powered down 434s (process:2247): libfprint-device-DEBUG: 05:09:14.263: Device reported close completion 434s (process:2247): libfprint-SSM-DEBUG: 05:09:14.263: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 434s (process:2247): libfprint-device-DEBUG: 05:09:14.263: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 434s (process:2247): libfprint-device-DEBUG: 05:09:14.263: Not updating temperature model, device can run continuously! 434s enrolling 434s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf3a55d48 (FpiDeviceSynaptics at 0xf10560)>, 1, None, None, None) 434s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf3a55d48 (FpiDeviceSynaptics at 0xf10560)>, 2, None, None, None) 434s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf3a55d48 (FpiDeviceSynaptics at 0xf10560)>, 3, None, None, None) 434s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf3a55d48 (FpiDeviceSynaptics at 0xf10560)>, 4, None, None, None) 434s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf3a55d48 (FpiDeviceSynaptics at 0xf10560)>, 5, None, None, None) 434s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf3a55d48 (FpiDeviceSynaptics at 0xf10560)>, 5, None, None, GLib.Error('Please try again.', 'fp - device - retry - quark', 0)) 434s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf3a55d48 (FpiDeviceSynaptics at 0xf10560)>, 6, None, None, None) 434s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf3a55d48 (FpiDeviceSynaptics at 0xf10560)>, 7, None, None, None) 434s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xf3a55d48 (FpiDeviceSynaptics at 0xf10560)>, 8, None, None, None) 434s enroll done 434s verifying 434s verify done 434s deleting 434s delete done 434s libusb: warning [libusb_exit] device 1.1 still referenced 434s ** (umockdev-run:2243): DEBUG: 05:09:14.291: umockdev.vala:154: Removing test bed /tmp/umockdev.DTVC22 434s (umockdev-run:2243): GLib-DEBUG: 05:09:14.297: unsetenv() is not thread-safe and should not be used after threads are created 434s PASS: libfprint-2/driver-synaptics.test 434s Running test: libfprint-2/driver-egis0570.test 434s ** (umockdev-run:2255): DEBUG: 05:09:14.357: umockdev.vala:127: Created udev test bed /tmp/umockdev.3LRG22 434s ** (umockdev-run:2255): DEBUG: 05:09:14.357: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 434s ** (umockdev-run:2255): DEBUG: 05:09:14.359: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 434s ** (umockdev-run:2255): DEBUG: 05:09:14.363: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3LRG22/dev/bus/usb/001/005 434s ** (umockdev-run:2255): DEBUG: 05:09:14.363: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 434s ** (umockdev-run:2255): DEBUG: 05:09:14.365: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 434s ** (umockdev-run:2255): DEBUG: 05:09:14.369: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3LRG22/dev/bus/usb/001/001 434s ** (umockdev-run:2255): DEBUG: 05:09:14.369: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 434s ** (umockdev-run:2255): DEBUG: 05:09:14.370: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 434s (process:2259): libfprint-context-DEBUG: 05:09:14.486: Initializing FpContext (libfprint version 1.94.9+tod1) 434s (process:2259): libfprint-tod-DEBUG: 05:09:14.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 434s (process:2259): libfprint-context-DEBUG: 05:09:14.490: No driver found for USB device 1D6B:0002 434s (process:2259): libfprint-device-DEBUG: 05:09:14.490: Device reported probe completion 434s (process:2259): libfprint-device-DEBUG: 05:09:14.490: Completing action FPI_DEVICE_ACTION_PROBE in idle! 434s (process:2259): libfprint-device-DEBUG: 05:09:14.490: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.492: Image device open completed 434s (process:2259): libfprint-device-DEBUG: 05:09:14.492: Device reported open completion 434s (process:2259): libfprint-device-DEBUG: 05:09:14.493: Completing action FPI_DEVICE_ACTION_OPEN in idle! 434s (process:2259): libfprint-device-DEBUG: 05:09:14.493: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 434s (process:2259): libfprint-device-DEBUG: 05:09:14.493: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.493: Activating image device 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.493: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.493: [egis0570] SM_STATES_NUM entering state 0 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.493: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.493: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.493: Image device activation completed 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.493: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.493: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 434s (process:2259): libfprint-device-DEBUG: 05:09:14.493: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.494: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.494: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.495: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.495: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.496: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.496: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.497: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.498: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.498: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.499: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.499: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.500: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.501: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.501: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.502: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.502: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.503: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.503: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.504: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.505: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.505: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.506: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.506: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.507: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.508: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.508: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.509: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.509: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.510: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.510: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.511: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.511: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.512: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.512: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.513: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.514: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.514: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.515: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.515: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.516: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.516: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.517: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.518: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.518: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.519: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.519: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.520: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.520: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.520: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.520: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.520: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.521: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.522: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.522: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.523: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.523: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.524: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.524: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.525: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.525: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.525: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.525: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.525: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.525: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.525: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.525: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.525: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.525: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.525: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.526: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.526: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.527: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.528: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.528: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.528: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.529: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.529: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.529: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.529: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.529: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.529: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.529: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.529: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.529: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.530: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.530: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.531: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.531: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.532: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.532: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.533: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.533: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.534: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.534: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.534: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.534: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.534: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.534: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.534: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.534: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.534: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.534: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.535: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.535: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.536: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.536: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.537: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.538: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.538: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.538: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.538: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.538: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.538: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.538: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.538: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.538: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.538: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.538: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.539: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.539: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.540: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.540: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.541: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.541: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.542: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.542: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.542: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.542: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.542: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.542: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.542: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.542: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.542: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.542: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.542: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.543: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.543: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.544: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.544: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.545: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.545: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.546: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.546: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.547: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.547: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.547: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.547: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.547: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.547: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.547: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.547: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.547: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.547: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.547: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.548: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.549: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.549: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.550: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.550: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.550: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.551: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.551: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.551: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.551: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.551: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.551: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.551: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.551: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.551: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.552: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.552: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.553: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.553: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.554: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.554: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.555: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.555: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.555: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.555: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.555: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.555: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.555: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.555: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.555: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.555: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.555: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.556: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.556: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.557: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.557: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.558: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.558: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.559: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.559: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.560: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.560: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.560: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.560: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.560: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.560: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.560: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.560: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.560: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.560: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.560: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.561: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.561: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.563: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.564: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.565: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.565: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.566: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.566: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.566: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.566: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.566: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.566: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.566: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.566: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.566: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.567: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.568: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.569: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.569: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.570: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.571: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.572: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.572: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.573: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.573: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.573: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.573: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.573: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.573: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.573: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.573: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.573: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.574: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.574: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.575: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.576: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.577: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.578: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.579: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.579: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.580: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.580: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.580: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.580: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.580: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.580: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.580: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.580: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.580: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.581: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.581: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.582: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.583: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.584: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.585: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.586: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.586: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.587: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.587: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.587: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.587: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.587: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.587: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.587: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.587: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.587: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.588: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.588: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.590: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.590: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.591: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.592: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-device-DEBUG: 05:09:14.593: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.593: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.593: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.594: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.594: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.594: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.594: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.594: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.594: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.594: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.594: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.594: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.595: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.596: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.597: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.597: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.598: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.599: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.600: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.600: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.601: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.601: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.601: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.601: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.601: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.601: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.601: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.601: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.601: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.602: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.603: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.604: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.605: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.606: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.606: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.607: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.607: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.608: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.608: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.608: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.608: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.608: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.608: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.608: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.608: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.608: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.609: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.609: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.610: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.611: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.612: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.612: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.614: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.614: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.615: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.615: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.615: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.615: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.615: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.615: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.615: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.615: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.615: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.615: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.616: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.617: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.617: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.619: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.619: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.620: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.620: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.621: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.621: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.621: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.621: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.621: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.621: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.621: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.621: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.621: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.622: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.623: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.624: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.624: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.625: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.626: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.627: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.627: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.628: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.628: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.628: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.628: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.628: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.628: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.628: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.628: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.628: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.629: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.630: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.631: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.632: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.633: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.633: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.635: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.635: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.636: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.636: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.636: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.636: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.636: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.636: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.636: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.636: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.636: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.636: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.637: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.638: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.638: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.640: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.640: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.641: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.641: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.642: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.642: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.642: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.642: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.642: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.642: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.642: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.642: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.642: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.645: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.646: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.647: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.647: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.648: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.648: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.650: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.650: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.651: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.651: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.651: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.651: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.651: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.651: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.651: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.651: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.651: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.651: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.652: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.653: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.653: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.654: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.655: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.656: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.656: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.657: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.657: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.657: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.657: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.657: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.657: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.657: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.657: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.657: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.658: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.658: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.660: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.660: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.661: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.662: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.663: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.663: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.664: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.664: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.664: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.664: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.664: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.664: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.664: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.664: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.664: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.665: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.665: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.666: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.666: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.667: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.668: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.669: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.669: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.670: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.670: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.670: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.670: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.670: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.670: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.670: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.670: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.670: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.671: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.672: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.673: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.674: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.675: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.675: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.676: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.676: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.677: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.677: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.677: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.677: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.677: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.677: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.677: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.677: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.678: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.678: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.679: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.680: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.680: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.681: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.682: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.683: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.683: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.684: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.684: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.684: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.684: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.684: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.684: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.684: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.684: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.684: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.685: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.685: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.686: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.687: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.688: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.688: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.689: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.690: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.691: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.691: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.691: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.691: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.691: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.691: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.691: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.691: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.691: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.691: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.692: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.693: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.694: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.695: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.695: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.696: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.696: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.698: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.698: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.698: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.698: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.698: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.698: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.698: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.698: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.698: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.698: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.699: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.700: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.701: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.702: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.702: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.703: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.703: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.704: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.704: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.704: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.704: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.704: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.704: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.704: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.704: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.704: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.705: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.706: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.707: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.707: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.708: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.709: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.710: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.710: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.711: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.711: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.711: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.711: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.711: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.711: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.711: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.711: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.711: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.712: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.712: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.713: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.714: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.715: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.715: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.716: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.716: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.717: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.717: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.717: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.717: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.717: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.717: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.717: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.717: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.717: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.718: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.718: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.720: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.720: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.721: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.721: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.723: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.723: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.724: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.724: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.724: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.724: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.724: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.724: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.724: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.724: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.724: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.726: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.726: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.728: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.729: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.730: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.730: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.731: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.732: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.733: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.733: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.733: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.733: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.733: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.733: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.733: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.733: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.733: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.734: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.734: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.736: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.736: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.737: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.738: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.738: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.738: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.739: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.739: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.739: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.739: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.739: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.739: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.739: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.739: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.739: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.740: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.740: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.741: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.741: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.742: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.742: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.743: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.743: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.744: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.744: Finger status (picture number, mean) : 1 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.744: Finger status (picture number, mean) : 2 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.744: Finger status (picture number, mean) : 3 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.744: Finger status (picture number, mean) : 4 , 0 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.744: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.744: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.744: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.744: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.744: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.745: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.745: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.746: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.747: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.747: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.748: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.748: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.748: Finger status (picture number, mean) : 0 , 0 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.748: Finger status (picture number, mean) : 1 , 1 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.748: Finger status (picture number, mean) : 2 , 2 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.748: Finger status (picture number, mean) : 3 , 3 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.748: Finger status (picture number, mean) : 4 , 6 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.748: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.748: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.748: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.748: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.749: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.749: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.750: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.750: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.751: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.752: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.752: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.752: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.753: Finger status (picture number, mean) : 0 , 11 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.753: Finger status (picture number, mean) : 1 , 16 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.753: Finger status (picture number, mean) : 2 , 23 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.753: Finger status (picture number, mean) : 3 , 28 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.753: Finger status (picture number, mean) : 4 , 32 434s (process:2259): libfprint-device-DEBUG: 05:09:14.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.753: Image device reported finger status: on 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.753: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 434s (process:2259): libfprint-device-DEBUG: 05:09:14.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.753: Image device reported finger status: off 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.753: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.753: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.753: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.754: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.754: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.755: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.755: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.756: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.756: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.757: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.757: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.758: Finger status (picture number, mean) : 0 , 38 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.758: Finger status (picture number, mean) : 1 , 43 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.758: Finger status (picture number, mean) : 2 , 48 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.758: Finger status (picture number, mean) : 3 , 54 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.758: Finger status (picture number, mean) : 4 , 58 434s (process:2259): libfprint-device-DEBUG: 05:09:14.758: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.758: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.758: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.758: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.758: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.758: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.759: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.759: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.760: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.760: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.761: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.761: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.761: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.762: Finger status (picture number, mean) : 0 , 62 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.762: Finger status (picture number, mean) : 1 , 68 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.762: Finger status (picture number, mean) : 2 , 71 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.762: Finger status (picture number, mean) : 3 , 73 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.762: Finger status (picture number, mean) : 4 , 77 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.762: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.762: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.762: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.762: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.763: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.763: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.764: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.764: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.765: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.765: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.766: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.766: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.767: Finger status (picture number, mean) : 0 , 79 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.767: Finger status (picture number, mean) : 1 , 79 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.767: Finger status (picture number, mean) : 2 , 82 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.767: Finger status (picture number, mean) : 3 , 84 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.767: Finger status (picture number, mean) : 4 , 85 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.767: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.767: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.767: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.767: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.767: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.767: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.768: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.768: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.769: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.770: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.770: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.770: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.771: Finger status (picture number, mean) : 0 , 88 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.771: Finger status (picture number, mean) : 1 , 89 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.771: Finger status (picture number, mean) : 2 , 90 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.771: Finger status (picture number, mean) : 3 , 92 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.771: Finger status (picture number, mean) : 4 , 92 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.771: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.771: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.771: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.771: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.771: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.772: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.773: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.773: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.774: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.774: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.775: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.775: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.775: Finger status (picture number, mean) : 0 , 93 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.775: Finger status (picture number, mean) : 1 , 94 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.775: Finger status (picture number, mean) : 2 , 95 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.775: Finger status (picture number, mean) : 3 , 96 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.775: Finger status (picture number, mean) : 4 , 97 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.775: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.775: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.775: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.775: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.776: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.776: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.777: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.777: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.778: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.779: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.779: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.779: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.780: Finger status (picture number, mean) : 0 , 97 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.780: Finger status (picture number, mean) : 1 , 95 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.780: Finger status (picture number, mean) : 2 , 95 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.780: Finger status (picture number, mean) : 3 , 96 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.780: Finger status (picture number, mean) : 4 , 97 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.780: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.780: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.780: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.780: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.780: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.781: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.781: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.782: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.783: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.783: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.784: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.784: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.784: Finger status (picture number, mean) : 0 , 96 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.784: Finger status (picture number, mean) : 1 , 97 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.784: Finger status (picture number, mean) : 2 , 98 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.784: Finger status (picture number, mean) : 3 , 98 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.784: Finger status (picture number, mean) : 4 , 98 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.784: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.784: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.784: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.784: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.785: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.785: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.786: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.786: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.787: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.787: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.788: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.788: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.789: Finger status (picture number, mean) : 0 , 98 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.789: Finger status (picture number, mean) : 1 , 99 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.789: Finger status (picture number, mean) : 2 , 100 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.789: Finger status (picture number, mean) : 3 , 99 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.789: Finger status (picture number, mean) : 4 , 97 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.789: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.789: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.789: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.789: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.789: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.790: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.790: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.791: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.791: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.792: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.792: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.793: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.793: Finger status (picture number, mean) : 0 , 98 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.793: Finger status (picture number, mean) : 1 , 98 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.793: Finger status (picture number, mean) : 2 , 98 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.793: Finger status (picture number, mean) : 3 , 95 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.793: Finger status (picture number, mean) : 4 , 91 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.793: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.793: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.793: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.793: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.794: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.794: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.795: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.795: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.796: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.796: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.797: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.797: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.798: Finger status (picture number, mean) : 0 , 88 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.798: Finger status (picture number, mean) : 1 , 88 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.798: Finger status (picture number, mean) : 2 , 88 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.798: Finger status (picture number, mean) : 3 , 87 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.798: Finger status (picture number, mean) : 4 , 89 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.798: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.798: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.798: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.798: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.798: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.798: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.799: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.799: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.800: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.801: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.801: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.801: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.802: Finger status (picture number, mean) : 0 , 88 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.802: Finger status (picture number, mean) : 1 , 89 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.802: Finger status (picture number, mean) : 2 , 90 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.802: Finger status (picture number, mean) : 3 , 91 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.802: Finger status (picture number, mean) : 4 , 89 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.802: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.802: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.802: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.802: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.802: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.803: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.803: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.804: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.805: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.805: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.806: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.806: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.806: Finger status (picture number, mean) : 0 , 90 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.806: Finger status (picture number, mean) : 1 , 89 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.806: Finger status (picture number, mean) : 2 , 85 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.806: Finger status (picture number, mean) : 3 , 75 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.806: Finger status (picture number, mean) : 4 , 46 434s (process:2259): libfprint-image_device-DEBUG: 05:09:14.806: Image device reported finger status: on 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.806: [egis0570] SM_STATES_NUM entering state 5 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.806: [egis0570] SM_STATES_NUM entering state 1 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.806: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.807: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.807: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.808: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.808: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.809: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.809: [egis0570] SM_STATES_NUM entering state 2 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.810: [egis0570] SM_STATES_NUM entering state 3 434s (process:2259): libfprint-SSM-DEBUG: 05:09:14.810: [egis0570] SM_STATES_NUM entering state 4 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.811: Finger status (picture number, mean) : 0 , 17 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.811: Finger status (picture number, mean) : 1 , 14 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.811: Finger status (picture number, mean) : 2 , 15 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.811: Finger status (picture number, mean) : 3 , 15 434s (process:2259): libfprint-egis0570-DEBUG: 05:09:14.811: Finger status (picture number, mean) : 4 , 15 434s (process:2259): libfprint-assembling-DEBUG: 05:09:14.889: calc delta completed in 0.078719 secs 435s (process:2259): libfprint-assembling-DEBUG: 05:09:14.969: calc delta completed in 0.080002 secs 435s (process:2259): libfprint-assembling-DEBUG: 05:09:14.969: errors: 10243 rev: 29954 435s (process:2259): libfprint-assembling-DEBUG: 05:09:15.049: calc delta completed in 0.079860 secs 435s (process:2259): libfprint-assembling-DEBUG: 05:09:15.049: height is 292 435s (process:2259): libfprint-image_device-DEBUG: 05:09:15.052: Image device captured an image 435s (process:2259): libfprint-image_device-DEBUG: 05:09:15.053: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 435s (process:2259): libfprint-device-DEBUG: 05:09:15.053: Device reported finger status change: FP_FINGER_STATUS_PRESENT 435s (process:2259): libfprint-device-DEBUG: 05:09:15.053: Device reported finger status change: FP_FINGER_STATUS_NONE 435s (process:2259): libfprint-image_device-DEBUG: 05:09:15.053: Image device reported finger status: off 435s (process:2259): libfprint-image_device-DEBUG: 05:09:15.053: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 435s (process:2259): libfprint-image_device-DEBUG: 05:09:15.053: Deactivating image device 435s (process:2259): libfprint-image_device-DEBUG: 05:09:15.053: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 435s (process:2259): libfprint-SSM-DEBUG: 05:09:15.053: [egis0570] SM_STATES_NUM entering state 5 435s (process:2259): libfprint-SSM-DEBUG: 05:09:15.053: [egis0570] SM_STATES_NUM entering state 1 435s (process:2259): libfprint-egis0570-DEBUG: 05:09:15.053: deactivating, marking completed 435s (process:2259): libfprint-SSM-DEBUG: 05:09:15.053: [egis0570] SM_STATES_NUM completed successfully 435s (process:2259): libfprint-image_device-DEBUG: 05:09:15.053: Image device deactivation completed 435s (process:2259): libfprint-image_device-DEBUG: 05:09:15.053: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 435s (process:2259): libfprint-image-DEBUG: 05:09:15.108: Minutiae scan completed in 0.054876 secs 435s (process:2259): libfprint-device-DEBUG: 05:09:15.109: Device reported capture completion 435s (process:2259): libfprint-device-DEBUG: 05:09:15.109: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 435s (process:2259): libfprint-device-DEBUG: 05:09:15.109: Updated temperature model after 0.52 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 435s (process:2259): libfprint-image_device-DEBUG: 05:09:15.109: Image device close completed 435s (process:2259): libfprint-device-DEBUG: 05:09:15.109: Device reported close completion 435s (process:2259): libfprint-device-DEBUG: 05:09:15.110: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 435s (process:2259): libfprint-device-DEBUG: 05:09:15.110: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 435s ** (umockdev-run:2255): DEBUG: 05:09:15.414: umockdev.vala:154: Removing test bed /tmp/umockdev.3LRG22 435s (umockdev-run:2255): GLib-DEBUG: 05:09:15.421: unsetenv() is not thread-safe and should not be used after threads are created 435s Comparing PNGs /tmp/libfprint-umockdev-test-0wlsej_j/capture.png and /usr/share/installed-tests/libfprint-2/egis0570/capture.png 435s PASS: libfprint-2/driver-egis0570.test 435s Running test: libfprint-2/driver-vfs0050.test 435s ** (umockdev-run:2268): DEBUG: 05:09:15.548: umockdev.vala:127: Created udev test bed /tmp/umockdev.CL4012 435s ** (umockdev-run:2268): DEBUG: 05:09:15.549: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 435s ** (umockdev-run:2268): DEBUG: 05:09:15.550: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 435s ** (umockdev-run:2268): DEBUG: 05:09:15.554: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.CL4012/dev/bus/usb/001/004 435s ** (umockdev-run:2268): DEBUG: 05:09:15.555: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 435s ** (umockdev-run:2268): DEBUG: 05:09:15.556: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 435s ** (umockdev-run:2268): DEBUG: 05:09:15.560: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.CL4012/dev/bus/usb/001/001 435s ** (umockdev-run:2268): DEBUG: 05:09:15.560: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 435s ** (umockdev-run:2268): DEBUG: 05:09:15.561: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 435s (umockdev-run:2268): GLib-GIO-DEBUG: 05:09:15.564: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 435s (process:2272): libfprint-context-DEBUG: 05:09:15.711: Initializing FpContext (libfprint version 1.94.9+tod1) 435s (process:2272): libfprint-tod-DEBUG: 05:09:15.711: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 435s (process:2272): libfprint-context-DEBUG: 05:09:15.715: No driver found for USB device 1D6B:0002 435s (process:2272): libfprint-device-DEBUG: 05:09:15.716: Device reported probe completion 435s (process:2272): libfprint-device-DEBUG: 05:09:15.716: Completing action FPI_DEVICE_ACTION_PROBE in idle! 435s (process:2272): libfprint-device-DEBUG: 05:09:15.716: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.718: [vfs0050] SSM_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.719: [vfs0050] SSM_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.720: [vfs0050] SSM_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.721: [vfs0050] SSM_STATES entering state 3 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.721: [vfs0050] SUBSM1_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.721: [vfs0050] SUBSM1_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.722: [vfs0050] SUBSM1_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.723: [vfs0050] SUBSM1_STATES completed successfully 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.723: [vfs0050] SSM_STATES entering state 4 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.723: [vfs0050] SUBSM2_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.723: [vfs0050] SUBSM2_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.724: [vfs0050] SUBSM2_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.725: [vfs0050] SUBSM2_STATES entering state 3 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.726: [vfs0050] SUBSM2_STATES entering state 4 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.726: [vfs0050] SUBSM2_STATES entering state 5 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.727: [vfs0050] SUBSM2_STATES entering state 6 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.727: [vfs0050] SUBSM1_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.728: [vfs0050] SUBSM1_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.728: [vfs0050] SUBSM1_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.729: [vfs0050] SUBSM1_STATES completed successfully 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.729: [vfs0050] SUBSM2_STATES completed successfully 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.729: [vfs0050] SSM_STATES entering state 5 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.729: [vfs0050] SSM_STATES completed successfully 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.729: Image device open completed 435s (process:2272): libfprint-device-DEBUG: 05:09:15.729: Device reported open completion 435s (process:2272): libfprint-device-DEBUG: 05:09:15.729: Completing action FPI_DEVICE_ACTION_OPEN in idle! 435s (process:2272): libfprint-device-DEBUG: 05:09:15.729: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 435s (process:2272): libfprint-device-DEBUG: 05:09:15.730: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.730: Activating image device 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.730: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.730: [vfs0050] SSM_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.730: [vfs0050] SSM_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.731: [vfs0050] SSM_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.732: [vfs0050] SSM_STATES entering state 3 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.732: [vfs0050] SUBSM1_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.732: [vfs0050] SUBSM1_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.733: [vfs0050] SUBSM1_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.733: [vfs0050] SUBSM1_STATES completed successfully 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.733: [vfs0050] SSM_STATES entering state 4 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.733: [vfs0050] SUBSM2_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.734: [vfs0050] SUBSM2_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.734: [vfs0050] SUBSM2_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.735: [vfs0050] SUBSM2_STATES entering state 3 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.735: [vfs0050] SUBSM2_STATES entering state 4 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.736: [vfs0050] SUBSM2_STATES entering state 5 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.736: [vfs0050] SUBSM2_STATES entering state 6 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.737: [vfs0050] SUBSM1_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.737: [vfs0050] SUBSM1_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.738: [vfs0050] SUBSM1_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.738: [vfs0050] SUBSM1_STATES completed successfully 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.738: [vfs0050] SUBSM2_STATES completed successfully 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.738: [vfs0050] SSM_STATES entering state 5 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.738: [vfs0050] SUBSM2_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.739: [vfs0050] SUBSM2_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.739: [vfs0050] SUBSM2_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.740: [vfs0050] SUBSM2_STATES entering state 3 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.740: [vfs0050] SUBSM2_STATES entering state 4 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.741: [vfs0050] SUBSM2_STATES entering state 5 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.741: [vfs0050] SUBSM2_STATES entering state 6 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.741: [vfs0050] SUBSM2_STATES completed successfully 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.741: [vfs0050] SSM_STATES entering state 6 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.741: Image device activation completed 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.741: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.741: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 435s (process:2272): libfprint-device-DEBUG: 05:09:15.741: Device reported finger status change: FP_FINGER_STATUS_NEEDED 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.741: [vfs0050] SSM_STATES entering state 7 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.742: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-device-DEBUG: 05:09:15.742: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.742: Image device reported finger status: on 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.742: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.742: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.743: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.744: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.745: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.745: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.746: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.747: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.747: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.748: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.749: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.749: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.750: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.751: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.751: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.752: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.753: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.753: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.754: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.755: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.755: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.756: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.757: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.757: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.758: [vfs0050] SSM_STATES entering state 8 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.758: [vfs0050] SSM_STATES entering state 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 1740200955759106 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 2 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 5 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 3 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 8 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 2 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 5 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 3 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 8 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 2 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 8 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 90 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 95 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 90 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 88 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 86 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 84 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 64 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 8 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 2 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 8 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 2 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 3 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.759: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 90 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 88 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 86 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 84 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 95 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 95 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 91 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 89 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 87 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 85 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 87 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 85 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 69 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 64 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 64 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 48 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 48 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.760: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.761: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 91 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 89 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 86 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.762: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.763: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 74 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.764: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 84 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 69 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 90 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 89 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 87 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 90 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 88 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 86 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 76 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 74 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 48 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 64 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 86 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 76 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.765: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 8 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 90 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 95 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 89 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 87 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 3 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 85 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 63 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 69 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 74 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 48 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 85 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 86 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 80 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 74 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 72 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 3 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 8 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 89 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 91 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 69 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.766: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 69 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 2 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 86 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 87 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 89 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 3 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 89 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 91 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 89 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 76 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 72 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 3 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 5 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 3 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 88 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 88 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 89 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 3 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 80 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 76 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 74 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 84 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 5 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 74 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 69 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 100 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 95 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 88 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 86 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 5 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 69 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.767: 63 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 84 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 95 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 84 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 63 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 5 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 5 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 3 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 8 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 2 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 2 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 2 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.768: 1 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: offsets_filtered: 1740200955769583 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 5 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 5 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 8 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 8 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 90 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 95 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 90 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 88 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 86 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 84 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.769: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 99 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 98 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 97 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 96 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 95 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 95 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 93 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 91 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 90 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 89 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 88 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 87 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 87 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 86 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 85 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 85 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 84 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 79 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 75 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 69 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 64 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 64 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 48 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.770: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 30 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.771: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 19 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 18 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 16 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 11 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 12 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 69 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 64 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 64 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 48 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.772: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 90 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 94 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 92 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 90 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 89 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 87 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 83 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 81 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 77 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 70 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 20 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 24 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 60 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 54 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 43 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 42 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 36 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 47 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 46 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 32 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 26 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 23 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 25 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 62 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 56 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 49 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 44 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 37 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 38 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 52 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 73 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 71 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 69 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 68 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 67 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 66 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 61 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 59 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 57 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 51 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 33 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 34 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 63 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 63 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.773: 63 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 63 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 65 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 63 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 58 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 55 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 50 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 53 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 45 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 41 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 40 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 39 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 35 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 31 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 29 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 28 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 27 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 22 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 21 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 17 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 15 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 14 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 13 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 10 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 9 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 8 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 7 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 4 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 6 435s (process:2272): libfprint-assembling-DEBUG: 05:09:15.774: 1 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.776: Image device captured an image 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.777: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 435s (process:2272): libfprint-device-DEBUG: 05:09:15.777: Device reported finger status change: FP_FINGER_STATUS_PRESENT 435s (process:2272): libfprint-device-DEBUG: 05:09:15.777: Device reported finger status change: FP_FINGER_STATUS_NONE 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.777: Image device reported finger status: off 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.777: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.777: Deactivating image device 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.777: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 435s (process:2272): libfprint-image-DEBUG: 05:09:15.818: Minutiae scan completed in 0.040923 secs 435s (process:2272): libfprint-device-DEBUG: 05:09:15.830: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.859: [vfs0050] SSM_STATES entering state 10 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.859: [vfs0050] SSM_STATES entering state 3 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.859: [vfs0050] SUBSM1_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.859: [vfs0050] SUBSM1_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.860: [vfs0050] SUBSM1_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.860: [vfs0050] SUBSM1_STATES completed successfully 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.860: [vfs0050] SSM_STATES entering state 4 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.860: [vfs0050] SUBSM2_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.861: [vfs0050] SUBSM2_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.861: [vfs0050] SUBSM2_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.862: [vfs0050] SUBSM2_STATES entering state 3 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.862: [vfs0050] SUBSM2_STATES entering state 4 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.863: [vfs0050] SUBSM2_STATES entering state 5 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.864: [vfs0050] SUBSM2_STATES entering state 6 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.864: [vfs0050] SUBSM1_STATES entering state 0 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.864: [vfs0050] SUBSM1_STATES entering state 1 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.865: [vfs0050] SUBSM1_STATES entering state 2 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.865: [vfs0050] SUBSM1_STATES completed successfully 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.866: [vfs0050] SUBSM2_STATES completed successfully 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.866: [vfs0050] SSM_STATES entering state 5 435s (process:2272): libfprint-SSM-DEBUG: 05:09:15.866: [vfs0050] SSM_STATES completed successfully 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.866: Image device deactivation completed 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.866: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 435s (process:2272): libfprint-device-DEBUG: 05:09:15.866: Device reported capture completion 435s (process:2272): libfprint-device-DEBUG: 05:09:15.866: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 435s (process:2272): libfprint-device-DEBUG: 05:09:15.866: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 435s (process:2272): libfprint-image_device-DEBUG: 05:09:15.866: Image device close completed 435s (process:2272): libfprint-device-DEBUG: 05:09:15.866: Device reported close completion 435s (process:2272): libfprint-device-DEBUG: 05:09:15.866: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 435s (process:2272): libfprint-device-DEBUG: 05:09:15.866: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 436s ** (umockdev-run:2268): DEBUG: 05:09:16.076: umockdev.vala:154: Removing test bed /tmp/umockdev.CL4012 436s (umockdev-run:2268): GLib-DEBUG: 05:09:16.083: unsetenv() is not thread-safe and should not be used after threads are created 436s Comparing PNGs /tmp/libfprint-umockdev-test-pspb8sp2/capture.png and /usr/share/installed-tests/libfprint-2/vfs0050/capture.png 436s PASS: libfprint-2/driver-vfs0050.test 436s Running test: libfprint-2/fp-device.test 436s TAP version 14 436s # random seed: R02Sadbd6ffa1b9639c7bc58c26010e3757f 436s 1..17 436s # Start of device tests 436s # Start of async tests 436s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 436s # 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 436s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 436s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 436s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 436s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-8W9E22/virtual_image.socket 436s # libfprint-context-DEBUG: created 436s # libfprint-device-DEBUG: Device reported probe completion 436s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 436s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:16.152: 131015145943: ../libfprint/drivers/virtual-image.c:216 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:16.152: 131015146079: ../libfprint/drivers/virtual-device-listener.c:153 436s # libfprint-image_device-DEBUG: Image device open completed 436s # libfprint-device-DEBUG: Device reported open completion 436s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 436s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:16.252: 131015246604: ../libfprint/drivers/virtual-image.c:244 436s # libfprint-image_device-DEBUG: Image device close completed 436s # libfprint-device-DEBUG: Device reported close completion 436s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 436s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 436s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 436s ok 1 /device/async/open 436s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 436s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 436s # 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 436s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 436s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 436s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 436s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-2NVG22/virtual_image.socket 436s # libfprint-context-DEBUG: created 436s # libfprint-device-DEBUG: Device reported probe completion 436s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 436s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:16.356: 131015350628: ../libfprint/drivers/virtual-image.c:216 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:16.356: 131015350657: ../libfprint/drivers/virtual-device-listener.c:153 436s # libfprint-image_device-DEBUG: Image device open completed 436s # libfprint-device-DEBUG: Device reported open completion 436s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 436s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:16.457: 131015451098: ../libfprint/drivers/virtual-image.c:244 436s # libfprint-image_device-DEBUG: Image device close completed 436s # libfprint-device-DEBUG: Device reported close completion 436s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 436s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 436s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 436s ok 2 /device/async/close 436s # End of async tests 436s # Start of sync tests 436s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 436s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 436s # 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 436s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 436s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 436s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 436s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-H9A212/virtual_image.socket 436s # libfprint-context-DEBUG: created 436s # libfprint-device-DEBUG: Device reported probe completion 436s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 436s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:16.561: 131015554924: ../libfprint/drivers/virtual-image.c:216 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:16.561: 131015554943: ../libfprint/drivers/virtual-device-listener.c:153 436s # libfprint-image_device-DEBUG: Image device open completed 436s # libfprint-device-DEBUG: Device reported open completion 436s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 436s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:16.661: 131015655510: ../libfprint/drivers/virtual-image.c:244 436s # libfprint-image_device-DEBUG: Image device close completed 436s # libfprint-device-DEBUG: Device reported close completion 436s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 436s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 436s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 436s ok 3 /device/sync/open 436s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 436s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 436s # 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 436s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 436s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 436s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 436s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-DTU312/virtual_image.socket 436s # libfprint-context-DEBUG: created 436s # libfprint-device-DEBUG: Device reported probe completion 436s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 436s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:16.765: 131015759445: ../libfprint/drivers/virtual-image.c:216 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:16.765: 131015759474: ../libfprint/drivers/virtual-device-listener.c:153 436s # libfprint-image_device-DEBUG: Image device open completed 436s # libfprint-device-DEBUG: Device reported open completion 436s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 436s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 436s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:16.866: 131015859936: ../libfprint/drivers/virtual-image.c:244 437s # libfprint-image_device-DEBUG: Image device close completed 437s # libfprint-device-DEBUG: Device reported close completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 437s ok 4 /device/sync/close 437s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 437s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 437s # 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 437s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 437s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 437s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 437s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-J4CA22/virtual_image.socket 437s # libfprint-context-DEBUG: created 437s # libfprint-device-DEBUG: Device reported probe completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:16.970: 131015963883: ../libfprint/drivers/virtual-image.c:216 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:16.970: 131015963903: ../libfprint/drivers/virtual-device-listener.c:153 437s # libfprint-image_device-DEBUG: Image device open completed 437s # libfprint-device-DEBUG: Device reported open completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:17.070: 131016064540: ../libfprint/drivers/virtual-image.c:244 437s # libfprint-image_device-DEBUG: Image device close completed 437s # libfprint-device-DEBUG: Device reported close completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 437s ok 5 /device/sync/get_driver 437s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 437s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 437s # 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 437s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 437s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 437s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 437s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-TU7F22/virtual_image.socket 437s # libfprint-context-DEBUG: created 437s # libfprint-device-DEBUG: Device reported probe completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:17.174: 131016168477: ../libfprint/drivers/virtual-image.c:216 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:17.174: 131016168497: ../libfprint/drivers/virtual-device-listener.c:153 437s # libfprint-image_device-DEBUG: Image device open completed 437s # libfprint-device-DEBUG: Device reported open completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:17.275: 131016269045: ../libfprint/drivers/virtual-image.c:244 437s # libfprint-image_device-DEBUG: Image device close completed 437s # libfprint-device-DEBUG: Device reported close completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 437s ok 6 /device/sync/get_device_id 437s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 437s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 437s # 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 437s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 437s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 437s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 437s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-5TSH22/virtual_image.socket 437s # libfprint-context-DEBUG: created 437s # libfprint-device-DEBUG: Device reported probe completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:17.379: 131016373266: ../libfprint/drivers/virtual-image.c:216 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:17.379: 131016373286: ../libfprint/drivers/virtual-device-listener.c:153 437s # libfprint-image_device-DEBUG: Image device open completed 437s # libfprint-device-DEBUG: Device reported open completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:17.480: 131016473824: ../libfprint/drivers/virtual-image.c:244 437s # libfprint-image_device-DEBUG: Image device close completed 437s # libfprint-device-DEBUG: Device reported close completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 437s ok 7 /device/sync/get_name 437s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 437s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 437s # 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 437s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 437s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 437s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 437s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-1QT112/virtual_image.socket 437s # libfprint-context-DEBUG: created 437s # libfprint-device-DEBUG: Device reported probe completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:17.584: 131016577732: ../libfprint/drivers/virtual-image.c:216 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:17.584: 131016577751: ../libfprint/drivers/virtual-device-listener.c:153 437s # libfprint-image_device-DEBUG: Image device open completed 437s # libfprint-device-DEBUG: Device reported open completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:17.684: 131016678203: ../libfprint/drivers/virtual-image.c:244 437s # libfprint-image_device-DEBUG: Image device close completed 437s # libfprint-device-DEBUG: Device reported close completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 437s ok 8 /device/sync/get_scan_type 437s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 437s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 437s # 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 437s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 437s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 437s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 437s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-JXE312/virtual_image.socket 437s # libfprint-context-DEBUG: created 437s # libfprint-device-DEBUG: Device reported probe completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:17.788: 131016782676: ../libfprint/drivers/virtual-image.c:216 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:17.788: 131016782707: ../libfprint/drivers/virtual-device-listener.c:153 437s # libfprint-image_device-DEBUG: Image device open completed 437s # libfprint-device-DEBUG: Device reported open completion 437s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 437s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 437s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:17.889: 131016883196: ../libfprint/drivers/virtual-image.c:244 437s Executing: libfprint-2/fp-device.test 438s # libfprint-image_device-DEBUG: Image device close completed 438s # libfprint-device-DEBUG: Device reported close completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 438s ok 9 /device/sync/get_finger_status 438s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 438s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 438s # 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 438s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 438s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 438s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 438s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-BYH812/virtual_image.socket 438s # libfprint-context-DEBUG: created 438s # libfprint-device-DEBUG: Device reported probe completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:17.993: 131016987639: ../libfprint/drivers/virtual-image.c:216 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:17.993: 131016987665: ../libfprint/drivers/virtual-device-listener.c:153 438s # libfprint-image_device-DEBUG: Image device open completed 438s # libfprint-device-DEBUG: Device reported open completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:18.094: 131017088181: ../libfprint/drivers/virtual-image.c:244 438s # libfprint-image_device-DEBUG: Image device close completed 438s # libfprint-device-DEBUG: Device reported close completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 438s ok 10 /device/sync/get_nr_enroll_stages 438s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 438s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 438s # 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 438s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 438s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 438s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 438s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-TD1F22/virtual_image.socket 438s # libfprint-context-DEBUG: created 438s # libfprint-device-DEBUG: Device reported probe completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:18.199: 131017193575: ../libfprint/drivers/virtual-image.c:216 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:18.199: 131017193596: ../libfprint/drivers/virtual-device-listener.c:153 438s # libfprint-image_device-DEBUG: Image device open completed 438s # libfprint-device-DEBUG: Device reported open completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:18.300: 131017294155: ../libfprint/drivers/virtual-image.c:244 438s # libfprint-image_device-DEBUG: Image device close completed 438s # libfprint-device-DEBUG: Device reported close completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 438s ok 11 /device/sync/supports_identify 438s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 438s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 438s # 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 438s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 438s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 438s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 438s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-SMFL22/virtual_image.socket 438s # libfprint-context-DEBUG: created 438s # libfprint-device-DEBUG: Device reported probe completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:18.404: 131017398307: ../libfprint/drivers/virtual-image.c:216 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:18.404: 131017398357: ../libfprint/drivers/virtual-device-listener.c:153 438s # libfprint-image_device-DEBUG: Image device open completed 438s # libfprint-device-DEBUG: Device reported open completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:18.505: 131017498809: ../libfprint/drivers/virtual-image.c:244 438s # libfprint-image_device-DEBUG: Image device close completed 438s # libfprint-device-DEBUG: Device reported close completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 438s ok 12 /device/sync/supports_capture 438s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 438s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 438s # 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 438s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 438s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 438s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 438s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-XWTZ12/virtual_image.socket 438s # libfprint-context-DEBUG: created 438s # libfprint-device-DEBUG: Device reported probe completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:18.609: 131017603271: ../libfprint/drivers/virtual-image.c:216 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:18.609: 131017603297: ../libfprint/drivers/virtual-device-listener.c:153 438s # libfprint-image_device-DEBUG: Image device open completed 438s # libfprint-device-DEBUG: Device reported open completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:18.710: 131017703768: ../libfprint/drivers/virtual-image.c:244 438s # libfprint-image_device-DEBUG: Image device close completed 438s # libfprint-device-DEBUG: Device reported close completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 438s ok 13 /device/sync/has_storage 438s # Start of open tests 438s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 438s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 438s # 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 438s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 438s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 438s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 438s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-4BQ612/virtual_image.socket 438s # libfprint-context-DEBUG: created 438s # libfprint-device-DEBUG: Device reported probe completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:18.814: 131017807819: ../libfprint/drivers/virtual-image.c:216 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:18.814: 131017807845: ../libfprint/drivers/virtual-device-listener.c:153 438s # libfprint-image_device-DEBUG: Image device open completed 438s # libfprint-device-DEBUG: Device reported open completion 438s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 438s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 438s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:18.914: 131017908241: ../libfprint/drivers/virtual-image.c:244 439s # libfprint-image_device-DEBUG: Image device close completed 439s # libfprint-device-DEBUG: Device reported close completion 439s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 439s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 439s ok 14 /device/sync/open/notify 439s # End of open tests 439s # Start of close tests 439s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 439s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 439s # 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 439s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 439s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 439s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 439s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-64VC22/virtual_image.socket 439s # libfprint-context-DEBUG: created 439s # libfprint-device-DEBUG: Device reported probe completion 439s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 439s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:19.018: 131018012363: ../libfprint/drivers/virtual-image.c:216 439s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:19.018: 131018012386: ../libfprint/drivers/virtual-device-listener.c:153 439s # libfprint-image_device-DEBUG: Image device open completed 439s # libfprint-device-DEBUG: Device reported open completion 439s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 439s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:19.119: 131018112871: ../libfprint/drivers/virtual-image.c:244 439s # libfprint-image_device-DEBUG: Image device close completed 439s # libfprint-device-DEBUG: Device reported close completion 439s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 439s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 439s ok 15 /device/sync/close/notify 439s # End of close tests 439s # Start of identify tests 439s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 439s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 439s # 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 439s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 439s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 439s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 439s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-YFQD22/virtual_image.socket 439s # libfprint-context-DEBUG: created 439s # libfprint-device-DEBUG: Device reported probe completion 439s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 439s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:19.223: 131018216921: ../libfprint/drivers/virtual-image.c:216 439s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:19.223: 131018216950: ../libfprint/drivers/virtual-device-listener.c:153 439s # libfprint-image_device-DEBUG: Image device open completed 439s # libfprint-device-DEBUG: Device reported open completion 439s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 439s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:19.323: 131018317645: ../libfprint/drivers/virtual-image.c:244 439s # libfprint-image_device-DEBUG: Image device close completed 439s # libfprint-device-DEBUG: Device reported close completion 439s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 439s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 439s ok 16 /device/sync/identify/cancelled 439s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 439s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 439s # 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 439s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 439s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 439s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 439s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-FKXK22/virtual_image.socket 439s # libfprint-context-DEBUG: created 439s # libfprint-device-DEBUG: Device reported probe completion 439s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 439s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:19.427: 131018421582: ../libfprint/drivers/virtual-image.c:216 439s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_device_connection-DEBUG: 05:09:19.427: 131018421608: ../libfprint/drivers/virtual-device-listener.c:153 439s # libfprint-image_device-DEBUG: Image device open completed 439s # libfprint-device-DEBUG: Device reported open completion 439s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 439s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2279): libfprint-virtual_image-DEBUG: 05:09:19.528: 131018522113: ../libfprint/drivers/virtual-image.c:244 439s # libfprint-image_device-DEBUG: Image device close completed 439s # libfprint-device-DEBUG: Device reported close completion 439s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 439s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 439s ok 17 /device/sync/identify/null-prints 439s # End of identify tests 439s # End of sync tests 439s # End of device tests 439s PASS: libfprint-2/fp-device.test 439s Running test: libfprint-2/driver-vfs5011.test 439s ** (umockdev-run:2319): DEBUG: 05:09:19.679: umockdev.vala:127: Created udev test bed /tmp/umockdev.SRW312 439s ** (umockdev-run:2319): DEBUG: 05:09:19.679: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2/2-6 439s ** (umockdev-run:2319): DEBUG: 05:09:19.680: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2/2-6 (subsystem usb) 439s ** (umockdev-run:2319): DEBUG: 05:09:19.684: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.SRW312/dev/bus/usb/002/017 439s ** (umockdev-run:2319): DEBUG: 05:09:19.684: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2 439s ** (umockdev-run:2319): DEBUG: 05:09:19.686: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2 (subsystem usb) 439s ** (umockdev-run:2319): DEBUG: 05:09:19.689: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.SRW312/dev/bus/usb/002/001 439s ** (umockdev-run:2319): DEBUG: 05:09:19.689: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 439s ** (umockdev-run:2319): DEBUG: 05:09:19.690: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 439s (umockdev-run:2319): GLib-GIO-DEBUG: 05:09:19.693: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 439s (process:2323): libfprint-context-DEBUG: 05:09:19.814: Initializing FpContext (libfprint version 1.94.9+tod1) 439s (process:2323): libfprint-tod-DEBUG: 05:09:19.814: Impossible to load the shared drivers dir Error opening directory “/usr/lib/arm-linux-gnueabihf/libfprint-2/tod-1”: No such file or directory 439s (process:2323): libfprint-context-DEBUG: 05:09:19.817: No driver found for USB device 1D6B:0002 439s (process:2323): libfprint-device-DEBUG: 05:09:19.817: Device reported probe completion 439s (process:2323): libfprint-device-DEBUG: 05:09:19.817: Completing action FPI_DEVICE_ACTION_PROBE in idle! 439s (process:2323): libfprint-device-DEBUG: 05:09:19.817: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.820: [vfs5011] DEV_OPEN_NUM_STATES entering state 0 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.820: [vfs5011] DEVICE OPEN entering state 0 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.820: Sending vfs5011_cmd_01 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.820: [vfs5011] DEVICE OPEN entering state 1 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.820: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.821: Got 38 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.821: [vfs5011] DEVICE OPEN entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.821: Sending vfs5011_cmd_19 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.822: [vfs5011] DEVICE OPEN entering state 3 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.822: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.822: Got 64 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.822: [vfs5011] DEVICE OPEN entering state 4 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.822: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.823: Got 4 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.823: [vfs5011] DEVICE OPEN entering state 5 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.823: Sending vfs5011_init_00 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.824: [vfs5011] DEVICE OPEN entering state 6 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.824: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.824: Got 6 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.824: [vfs5011] DEVICE OPEN entering state 7 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.824: Sending vfs5011_init_01 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.825: [vfs5011] DEVICE OPEN entering state 8 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.825: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.825: Got 7 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.825: [vfs5011] DEVICE OPEN entering state 9 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.825: Sending vfs5011_init_02 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.826: [vfs5011] DEVICE OPEN entering state 10 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.826: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.827: [vfs5011] DEVICE OPEN entering state 11 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.827: Sending vfs5011_cmd_01 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.827: [vfs5011] DEVICE OPEN entering state 12 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.827: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.828: Got 38 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.828: [vfs5011] DEVICE OPEN entering state 13 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.828: Sending vfs5011_cmd_1A 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.828: [vfs5011] DEVICE OPEN entering state 14 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.828: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.829: [vfs5011] DEVICE OPEN entering state 15 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.829: Sending vfs5011_init_03 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.830: [vfs5011] DEVICE OPEN entering state 16 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.830: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.830: [vfs5011] DEVICE OPEN entering state 17 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.830: Sending vfs5011_init_04 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.831: [vfs5011] DEVICE OPEN entering state 18 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.831: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.832: [vfs5011] DEVICE OPEN entering state 19 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.832: Receiving 256 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.832: Got 256 bytes out of 256 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.832: [vfs5011] DEVICE OPEN entering state 20 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.832: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.833: Got 32 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.833: [vfs5011] DEVICE OPEN entering state 21 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.833: Sending vfs5011_cmd_1A 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.834: [vfs5011] DEVICE OPEN entering state 22 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.834: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.834: [vfs5011] DEVICE OPEN entering state 23 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.834: Sending vfs5011_init_05 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.835: [vfs5011] DEVICE OPEN entering state 24 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.835: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.836: [vfs5011] DEVICE OPEN entering state 25 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.836: Sending vfs5011_cmd_01 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.836: [vfs5011] DEVICE OPEN entering state 26 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.836: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.837: Got 38 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.837: [vfs5011] DEVICE OPEN entering state 27 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.837: Sending vfs5011_init_06 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.838: [vfs5011] DEVICE OPEN entering state 28 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.838: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.838: [vfs5011] DEVICE OPEN entering state 29 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.838: Receiving 17216 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.839: Got 17216 bytes out of 17216 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.839: [vfs5011] DEVICE OPEN entering state 30 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.839: Receiving 32 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.839: Got 32 bytes out of 32 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.839: [vfs5011] DEVICE OPEN entering state 31 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.839: Sending vfs5011_init_07 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.840: [vfs5011] DEVICE OPEN entering state 32 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.840: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.841: [vfs5011] DEVICE OPEN entering state 33 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.841: Receiving 45056 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.841: Got 45056 bytes out of 45056 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.842: [vfs5011] DEVICE OPEN entering state 34 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.842: Sending vfs5011_init_08 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.842: [vfs5011] DEVICE OPEN entering state 35 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.842: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.843: [vfs5011] DEVICE OPEN entering state 36 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.843: Receiving 16896 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.843: Got 16896 bytes out of 16896 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.844: [vfs5011] DEVICE OPEN entering state 37 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.844: Sending vfs5011_init_09 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.844: [vfs5011] DEVICE OPEN entering state 38 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.844: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.845: [vfs5011] DEVICE OPEN entering state 39 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.845: Receiving 4928 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.845: Got 4928 bytes out of 4928 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.845: [vfs5011] DEVICE OPEN entering state 40 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.845: Sending vfs5011_init_10 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.846: [vfs5011] DEVICE OPEN entering state 41 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.846: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.847: [vfs5011] DEVICE OPEN entering state 42 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.847: Receiving 5632 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.847: Got 5632 bytes out of 5632 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.847: [vfs5011] DEVICE OPEN entering state 43 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.847: Sending vfs5011_init_11 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.848: [vfs5011] DEVICE OPEN entering state 44 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.848: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.849: [vfs5011] DEVICE OPEN entering state 45 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.849: Receiving 5632 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.849: Got 5632 bytes out of 5632 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.849: [vfs5011] DEVICE OPEN entering state 46 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.849: Sending vfs5011_init_12 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.850: [vfs5011] DEVICE OPEN entering state 47 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.850: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.851: [vfs5011] DEVICE OPEN entering state 48 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.851: Receiving 3328 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.851: Got 3328 bytes out of 3328 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.851: [vfs5011] DEVICE OPEN entering state 49 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.851: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.852: Got 32 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.852: [vfs5011] DEVICE OPEN entering state 50 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.852: Sending vfs5011_init_13 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.853: [vfs5011] DEVICE OPEN entering state 51 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.853: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.853: [vfs5011] DEVICE OPEN entering state 52 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.853: Sending vfs5011_cmd_1A 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.854: [vfs5011] DEVICE OPEN entering state 53 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.854: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.855: [vfs5011] DEVICE OPEN entering state 54 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.855: Sending vfs5011_init_03 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.855: [vfs5011] DEVICE OPEN entering state 55 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.855: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.856: [vfs5011] DEVICE OPEN entering state 56 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.856: Sending vfs5011_init_14 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.857: [vfs5011] DEVICE OPEN entering state 57 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.857: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.857: [vfs5011] DEVICE OPEN entering state 58 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.857: Receiving 4800 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.858: Got 4800 bytes out of 4800 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.858: [vfs5011] DEVICE OPEN entering state 59 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.858: Sending vfs5011_cmd_1A 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.859: [vfs5011] DEVICE OPEN entering state 60 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.859: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.859: [vfs5011] DEVICE OPEN entering state 61 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.859: Sending vfs5011_init_02 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.860: [vfs5011] DEVICE OPEN entering state 62 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.860: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.861: [vfs5011] DEVICE OPEN entering state 63 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.861: Sending vfs5011_cmd_27 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.861: [vfs5011] DEVICE OPEN entering state 64 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.861: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.862: Got 22 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.862: [vfs5011] DEVICE OPEN entering state 65 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.862: Sending vfs5011_cmd_1A 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.863: [vfs5011] DEVICE OPEN entering state 66 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.863: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.863: [vfs5011] DEVICE OPEN entering state 67 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.863: Sending vfs5011_init_15 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.864: [vfs5011] DEVICE OPEN entering state 68 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.864: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.865: [vfs5011] DEVICE OPEN entering state 69 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.865: Sending vfs5011_init_16 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.865: [vfs5011] DEVICE OPEN entering state 70 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.865: Receiving 2368 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.866: Got 2368 bytes out of 2368 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.866: [vfs5011] DEVICE OPEN entering state 71 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.866: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.867: Got 36 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.867: [vfs5011] DEVICE OPEN entering state 72 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.867: Receiving 4800 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.867: Got 4800 bytes out of 4800 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.867: [vfs5011] DEVICE OPEN entering state 73 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.867: Sending vfs5011_init_17 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.868: [vfs5011] DEVICE OPEN entering state 74 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.868: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.869: [vfs5011] DEVICE OPEN entering state 75 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.869: Sending vfs5011_init_18 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.869: [vfs5011] DEVICE OPEN entering state 76 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.869: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.870: [vfs5011] DEVICE OPEN completed successfully 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.870: [vfs5011] DEV_OPEN_NUM_STATES completed successfully 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.870: Image device open completed 439s (process:2323): libfprint-device-DEBUG: 05:09:19.870: Device reported open completion 439s (process:2323): libfprint-device-DEBUG: 05:09:19.870: Completing action FPI_DEVICE_ACTION_OPEN in idle! 439s (process:2323): libfprint-device-DEBUG: 05:09:19.870: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s (process:2323): libfprint-device-DEBUG: 05:09:19.870: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.870: Activating image device 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.870: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.870: device initialized 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.870: creating ssm 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.870: starting ssm 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.870: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 0 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.870: main_loop: state 0 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.870: [vfs5011] ACTIVATE REQUEST entering state 0 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.871: Sending vfs5011_cmd_04 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.871: ssm done, getting out 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.871: [vfs5011] ACTIVATE REQUEST entering state 1 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.871: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.872: Got 64 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.872: [vfs5011] ACTIVATE REQUEST entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.872: Receiving 84032 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.873: Got 176 bytes out of 84032 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.873: [vfs5011] ACTIVATE REQUEST entering state 3 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.873: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.873: [vfs5011] ACTIVATE REQUEST entering state 4 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.873: Sending vfs5011_cmd_1A 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.874: [vfs5011] ACTIVATE REQUEST entering state 5 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.874: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.875: [vfs5011] ACTIVATE REQUEST entering state 6 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.875: Sending vfs5011_prepare_00 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.875: [vfs5011] ACTIVATE REQUEST entering state 7 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.875: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.876: [vfs5011] ACTIVATE REQUEST entering state 8 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.876: Sending vfs5011_cmd_1A 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.877: [vfs5011] ACTIVATE REQUEST entering state 9 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.877: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.877: [vfs5011] ACTIVATE REQUEST entering state 10 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.877: Sending vfs5011_prepare_01 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.878: [vfs5011] ACTIVATE REQUEST entering state 11 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.878: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.878: [vfs5011] ACTIVATE REQUEST entering state 12 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.878: Sending vfs5011_prepare_02 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.879: [vfs5011] ACTIVATE REQUEST entering state 13 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.879: Receiving 2368 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.880: Got 2368 bytes out of 2368 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.880: [vfs5011] ACTIVATE REQUEST entering state 14 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.880: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.880: Got 36 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.880: [vfs5011] ACTIVATE REQUEST entering state 15 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.880: Receiving 4800 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.881: Got 4800 bytes out of 4800 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.881: [vfs5011] ACTIVATE REQUEST entering state 16 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.881: Sending vfs5011_prepare_03 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.882: [vfs5011] ACTIVATE REQUEST entering state 17 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.882: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.882: [vfs5011] ACTIVATE REQUEST entering state 18 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.882: Sending vfs5011_prepare_04 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.883: [vfs5011] ACTIVATE REQUEST entering state 19 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.883: Receiving 2368 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.884: [vfs5011] ACTIVATE REQUEST completed successfully 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.884: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 1 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.884: main_loop: state 1 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.884: capture_init 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.884: Image device activation completed 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.884: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.884: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 439s (process:2323): libfprint-device-DEBUG: 05:09:19.884: Device reported finger status change: FP_FINGER_STATUS_NEEDED 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.884: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.884: main_loop: state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.884: capture_chunk_async: capture 256 lines, already have 0 439s (process:2323): libfprint-device-DEBUG: 05:09:19.884: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.884: Image device reported finger status: on 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.884: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.884: process_chunk: got 61440 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.884: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.884: main_loop: state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.884: capture_chunk_async: capture 256 lines, already have 6 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.885: Image device reported finger status: on 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.885: process_chunk: got 61440 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.885: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.885: main_loop: state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.885: capture_chunk_async: capture 256 lines, already have 25 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.886: Image device reported finger status: on 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.886: process_chunk: got 61440 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.886: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.886: main_loop: state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.886: capture_chunk_async: capture 256 lines, already have 54 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.887: Image device reported finger status: on 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.887: process_chunk: got 61440 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.887: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.887: main_loop: state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.887: capture_chunk_async: capture 256 lines, already have 89 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.888: Image device reported finger status: on 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.888: process_chunk: got 61440 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.888: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.888: main_loop: state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.888: capture_chunk_async: capture 256 lines, already have 117 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.889: Image device reported finger status: on 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.889: process_chunk: got 61440 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.889: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.889: main_loop: state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.889: capture_chunk_async: capture 256 lines, already have 144 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.890: Image device reported finger status: on 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.890: process_chunk: got 61440 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.890: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.890: main_loop: state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.890: capture_chunk_async: capture 256 lines, already have 180 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.891: Image device reported finger status: on 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.891: process_chunk: got 61440 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.891: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.891: main_loop: state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.891: capture_chunk_async: capture 256 lines, already have 273 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.892: Image device reported finger status: on 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.892: process_chunk: got 61440 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.892: process_chunk: got 50 empty lines, finishing 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.892: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 3 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.892: main_loop: state 3 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.893: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 4 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.893: main_loop: state 4 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.893: [vfs5011] PREPARE CAPTURE entering state 0 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.893: Sending vfs5011_cmd_04 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.893: [vfs5011] PREPARE CAPTURE entering state 1 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.893: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.894: Got 64 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.894: [vfs5011] PREPARE CAPTURE entering state 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.894: Receiving 84032 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.895: Got 176 bytes out of 84032 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.895: [vfs5011] PREPARE CAPTURE entering state 3 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.895: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.895: [vfs5011] PREPARE CAPTURE entering state 4 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.895: Sending vfs5011_cmd_1A 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.896: [vfs5011] PREPARE CAPTURE entering state 5 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.896: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.897: [vfs5011] PREPARE CAPTURE entering state 6 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.897: Sending vfs5011_prepare_00 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.897: [vfs5011] PREPARE CAPTURE entering state 7 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.897: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.898: [vfs5011] PREPARE CAPTURE entering state 8 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.898: Sending vfs5011_cmd_1A 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.898: [vfs5011] PREPARE CAPTURE entering state 9 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.898: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.899: [vfs5011] PREPARE CAPTURE entering state 10 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.899: Sending vfs5011_prepare_01 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.899: [vfs5011] PREPARE CAPTURE entering state 11 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.899: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.900: [vfs5011] PREPARE CAPTURE entering state 12 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.900: Sending vfs5011_prepare_02 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.901: [vfs5011] PREPARE CAPTURE entering state 13 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.901: Receiving 2368 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.901: Got 2368 bytes out of 2368 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.901: [vfs5011] PREPARE CAPTURE entering state 14 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.901: Receiving 64 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.902: Got 36 bytes out of 64 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.902: [vfs5011] PREPARE CAPTURE entering state 15 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.902: Receiving 4800 bytes 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.903: Got 4800 bytes out of 4800 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.903: [vfs5011] PREPARE CAPTURE entering state 16 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.903: Sending vfs5011_prepare_03 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.903: [vfs5011] PREPARE CAPTURE entering state 17 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.903: Receiving 64 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.904: [vfs5011] PREPARE CAPTURE entering state 18 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.904: Sending vfs5011_prepare_04 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.904: [vfs5011] PREPARE CAPTURE entering state 19 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.904: Receiving 2368 bytes 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.905: [vfs5011] PREPARE CAPTURE completed successfully 439s (process:2323): libfprint-SSM-DEBUG: 05:09:19.905: [vfs5011] DEV_ACTIVATE_NUM_STATES completed successfully 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.905: finishing 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 1740200959905526 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 1 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 5 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 4 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 4 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 3 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 3 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 5 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 4 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 5 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 5 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 5 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 4 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 4 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.905: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 11 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 30 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 26 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 5 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 4 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 2 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: offsets_filtered: 1740200959906542 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 5 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 5 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 5 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 5 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 5 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 27 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 29 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 28 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 6 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 9 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 8 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 7 439s (process:2323): libfprint-assembling-DEBUG: 05:09:19.906: 2 439s (process:2323): libfprint-vfs5011-DEBUG: 05:09:19.907: Image captured, committing 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.907: Image device captured an image 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.909: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 439s (process:2323): libfprint-device-DEBUG: 05:09:19.909: Device reported finger status change: FP_FINGER_STATUS_PRESENT 439s (process:2323): libfprint-device-DEBUG: 05:09:19.909: Device reported finger status change: FP_FINGER_STATUS_NONE 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.909: Image device reported finger status: off 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.909: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.909: Deactivating image device 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.909: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.909: Image device deactivation completed 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.909: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 439s (process:2323): libfprint-image-DEBUG: 05:09:19.926: Minutiae scan completed in 0.016661 secs 439s (process:2323): libfprint-device-DEBUG: 05:09:19.926: Device reported capture completion 439s (process:2323): libfprint-device-DEBUG: 05:09:19.926: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 439s (process:2323): libfprint-device-DEBUG: 05:09:19.926: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 439s (process:2323): libfprint-image_device-DEBUG: 05:09:19.926: Image device close completed 439s (process:2323): libfprint-device-DEBUG: 05:09:19.926: Device reported close completion 439s (process:2323): libfprint-device-DEBUG: 05:09:19.926: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 439s (process:2323): libfprint-device-DEBUG: 05:09:19.926: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 440s ** (umockdev-run:2319): DEBUG: 05:09:20.035: umockdev.vala:154: Removing test bed /tmp/umockdev.SRW312 440s (umockdev-run:2319): GLib-DEBUG: 05:09:20.042: unsetenv() is not thread-safe and should not be used after threads are created 440s Comparing PNGs /tmp/libfprint-umockdev-test-k_adfzhk/capture.png and /usr/share/installed-tests/libfprint-2/vfs5011/capture.png 440s PASS: libfprint-2/driver-vfs5011.test 440s SUMMARY: total=36; passed=36; skipped=0; failed=0; user=25.7s; system=13.1s; maxrss=35040 440s autopkgtest [05:09:20]: test installed-tests: -----------------------] 445s autopkgtest [05:09:25]: test installed-tests: - - - - - - - - - - results - - - - - - - - - - 445s installed-tests PASS 449s autopkgtest [05:09:29]: @@@@@@@@@@@@@@@@@@@@ summary 449s installed-tests PASS